Скачать или смотреть Fixing Your Azure CI Pipeline for Blazor .NET 5

Learn how to resolve issues in your Azure CI pipeline when upgrading your Blazor application to .NET 5. This guide provides step-by-step instructions to ensure successful builds and deployments.
---
This video is based on the question https://stackoverflow.com/q/64232919/ asked by the user 'Andrea' ( https://stackoverflow.com/u/583523/ ) and on the answer https://stackoverflow.com/a/64260329/ provided by the user 'Akinzekeel' ( https://stackoverflow.com/u/2748326/ ) 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: Azure CI pipeline for Blazor .NET 5 doesn't work

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.
---
Fixing Your Azure CI Pipeline for Blazor .NET 5: A Comprehensive Guide

When it comes to Continuous Integration (CI) in Azure, many developers encounter challenges during upgrades – especially in complex frameworks like Blazor. Recently, a user upgraded their Blazor WebAssembly application from .NET Core 3.1 to .NET 5. However, the Azure CI pipeline that previously worked without issues began to fail. Let’s dive into the details of this problem and explore a robust solution.

The Issue

After upgrading to .NET 5 RC, the user's Azure CI pipeline failed to locate the necessary .NET Core SDK. The error messages indicated problems with locating the SDK and building the solution. For context, here are the critical error messages:

Unable to locate the .NET Core SDK.

The SDK 'Microsoft.NET.Sdk.Web' specified could not be found.

This indicates that Azure Pipelines could not find the required SDK for building the Blazor project.

Troubleshooting Steps

To resolve the issue, the user followed these steps:

Removed the existing NuGet task.

Inserted the new tasks for using .NET 5 and restoring the project.

However, while these steps were on the right track, additional configuration was necessary, mainly to ensure the correct VS version and SDK installation.

Solution: Updating the Azure Pipeline Configuration

Step 1: Modify the UseDotNet Task

The first action to take is to ensure that the correct version of the .NET SDK is being utilized. Update the UseDotNet task in your Azure pipeline configuration as follows:

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

Step 2: Full YAML Pipeline Configuration

Here’s a complete example of an Azure Pipeline YAML configuration that is known to work with Blazor and .NET 5:

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

Step 3: Additional Tips

Check global.json: If your project contains a global.json file, ensure that it specifies the correct SDK version.

Environment Variables: If you encounter issues with path variables, consider setting up the MSBuildSDKsPath. However, ensure that this doesn’t conflict with the environment variable used during the restore task.

Documentation: Keep an eye on the documentation for .NET 5 and Azure, as updates can shift some configurations.

Conclusion

Upgrading to .NET 5 can seem daunting, but with the right configurations in your Azure CI pipeline, you can streamline the process and avoid disruptions. By ensuring that the correct SDK version is being used and following the detailed steps shared in this guide, you can successfully build and deploy your Blazor applications.

In conclusion, tackling CI issues involves patience and a systematic approach. If you encounter other issues, don’t hesitate to consult the Azure documentation or community for further assistance.