Скачать или смотреть Deploying a dotnet6 Project with WebJobs in Azure App Service

Learn how to deploy your `dotnet6` project along with WebJobs in Azure App Service using Azure DevOps and YAML configuration.
---
This video is based on the question https://stackoverflow.com/q/75429864/ asked by the user 'Hamid' ( https://stackoverflow.com/u/20664456/ ) and on the answer https://stackoverflow.com/a/75460883/ provided by the user 'Hamid' ( https://stackoverflow.com/u/20664456/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: CICD Yaml in Azure Devops for : dotnet6 project with some WebJobs into AppService in Azure

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Deploying a dotnet6 Project with WebJobs in Azure App Service: A Complete Guide

Azure DevOps offers a powerful platform for continuous integration and continuous deployment (CI/CD), making it an attractive choice for developers deploying applications to Azure. If you're working with a dotnet6 project that also includes WebJobs, you might encounter challenges when trying to deploy both components together in a single App Service slot. This post will walk you through the solution, breaking it down into manageable sections so you can deploy effortlessly.

The Problem Statement

As you set up your Azure DevOps pipelines, you may find yourself in the following situation:

You have a dotnet6 project that you're deploying to Azure App Service.

Along with the project, you also have WebJobs that need to be deployed to the same App Service slot.

The CI process generates a ZIP file containing your main application, including other relevant files such as Parameters.xml, SetParameters.xml, and a deployment script.

The deployment task (e.g., AzureRmWebAppDeployment@ 4) allows for the deployment of only one ZIP file per execution. Therefore, deploying both your WebApp and WebJobs might result in one overriding the other.

Your initial attempts may include creating separate ZIPs for both the WebApp and WebJobs; however, the deployment would not succeed as expected. Thankfully, there is a solution.

The Solution

To successfully deploy both your dotnet6 application and WebJobs to the same App Service slot without conflict, follow these steps:

1. Generate Appropriate ZIP Files

You need to ensure that you have separate ZIP files for your WebApp and WebJobs. Below is an updated YAML configuration to show you how to set this up:

[[See Video to Reveal this Text or Code Snippet]]

2. Deploying ZIP Files

Now that you have generated the necessary ZIP files for both components, the next step is the deployment. You'll need to execute the AzureRmWebAppDeployment@ 4 task twice: once for your primary WebApp and once for the WebJobs. Furthermore, make sure to adjust parameters to avoid conflicts between deployments:

[[See Video to Reveal this Text or Code Snippet]]

Important Parameters

enableCustomDeployment: Set this to true for the second deployment task (the WebJobs) to allow custom settings during the deployment process.

ExcludeFilesFromAppDataFlag: Set this to false to ensure the WebJobs are treated correctly without overwriting existing configurations.

Conclusion

By following this structured approach, you can efficiently deploy a dotnet6 application alongside WebJobs in the same Azure App Service slot without issues related to file overriding. Clear separation of ZIP files coupled with adjusted deployment parameters ensures everything runs smoothly together.

Now, you have the tools necessary to handle deployments in Azure DevOps effectively. Happy coding!