Skip to main content

Azure Web Jobs Installer

I’m currently working on a project where we want to use the WebJobs feature of Azure Websites. Azure WebJobs enables you to run programs or scripts in your web site either continuously, on demand or on a schedule.

I really like this feature, the only thing annoying is that you have to deploy your web jobs separately. You cannot use Web Deploy and deploy it together with your Azure Website.

Thanks to the WebJobsVS extension this is no longer true, and you get a way to deploy your web job together with your website.

From the site:

With this extension you can right click on a web project in Visual Studio and associate a console project as a WebJob. After doing that when you publish the web project the webjob project will be published into the correct location in your Azure Web Site.

After selecting this you will see the following dialog.

In this dialog you'll select the console project which contains your webjob and specify the schedule for the webjob. If you are using the WebJobs SDK most likley you will want to chose Continious here. After you do this the following changes will be made the the web project.

  1. A reference will be added to the console project
  2. In the web project the WebJobsBuilder NuGet package is installed
  3. In the web project a readme.txt file will be created at App_Data\jobs\continuous\<project-name>

The WebJobsBuilder NuGet package contains an MSBuild .targets file that is added to the projects build/publish process. This is what extends the publish process to consume the output of the webjob project.

Nice one! Hopefully this will be an integrated part of the Windows Azure SDK soon…

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more