Andrew Hoefling

Speaker | Mentor | Coder | Leader

Using Conditional Insertion in Azure Pipelines allows a build to insert build tasks depending on parameters. This differs than a conditional task becaues it can remove or add the task to the build task list. This means you can completely customize the build tasks and only show the ones that the build is interested in.

More and more build scenarios using Azure Pipelines require complex customization which have been simplified by the Configuration As Code feature that has been available in Azure DevOps for a couple years now. When making the switch from the GUI to YAML I sturggled quite a bit with build numbers not working the same exact way since you can't customize the Version Number.

Deploying a .NET Framework WebJob to Azure is easy enough, but as of writing this blog the tooling is lacking for .NET Core. Many organizations are making it an initiative to migrate their .NET Framework projects to .NET Core which is a good idea. The tooling limitation for .NET Core WebJobs should not be a barrier, following this guide you will be able to deploy your .NET Core WebJobs to Azure