Скачать или смотреть Resolving .NET 5 Pipeline Build Issues with Azure DevOps

Learn how to resolve the issue of building a `.NET 5` project in Azure DevOps pipelines, with a focus on NuGet version changes and MSBuild compatibility
---
This video is based on the question https://stackoverflow.com/q/64848744/ asked by the user 'waleed' ( https://stackoverflow.com/u/9905699/ ) and on the answer https://stackoverflow.com/a/64848870/ provided by the user 'waleed' ( https://stackoverflow.com/u/9905699/ ) 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: Can't build .Net 5 in pipeline

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.
---
Can't Build .NET 5 in Azure DevOps Pipeline? Here's the Solution!

If you're using Azure DevOps pipelines to build your .NET 5 projects, you may have faced frustrations, particularly with compatibility issues during the build process. One common error is related to package compatibility during the NuGet restore phase, manifesting with messages indicating that your project is trying to use an older version of the .NET Framework instead of .NET 5. In this guide, we will walk through the solution to this problem step-by-step, so you can get back to developing your application with ease.

The Problem Explained

When trying to build a new solution created with .NET 5 RC2 and upgraded to the official 5.0.0 release, many developers encounter build errors in Azure Pipelines. The error logs are filled with messages indicating that specific packages (like Microsoft.EntityFrameworkCore.SqlServer) are not compatible with .NET 5 but rather with .NETStandard 2.1. This can lead to significant roadblocks, halting your development process.

Common Error Messages

Here are some typical error messages you may encounter:

Package Microsoft.EntityFrameworkCore.SqlServer 5.0.0 is not compatible with net50 (.NETFramework,Version=v5.0)

Incompatible packages: 4

Packages failed to restore

These errors suggest that the pipeline is trying to use outdated versions of NuGet or MSBuild, leading to compatibility issues.

The Solution: Upgrade NuGet and Use Correct Tasks

Step 1: Update the NuGet Version

The key to resolving the compatibility issue is ensuring that your .NET 5 project is using an updated version of NuGet. The older version can default to using incompatible package versions. Follow the steps below to update NuGet in your pipeline configuration:

Edit your Azure Pipeline YAML file to specify using the latest NuGet version. For example, change the task to use version 5.x.x before the restore step:

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

Step 2: Use .NET 5 with Dotnet Build

Another issue developers ran into was related to MSBuild version. If MSBuild 16.8 hasn't been released in your environment, you may need to adapt your build process to utilize the dotnet build command instead. To implement this:

Add the Dotnet Task: Precede your build step with the Use Dotnet 5 task in your YAML configuration to guarantee that the correct version of the .NET Core SDK is used.

Example Modified Pipeline

Here is a brief example of how your YAML configuration might look after the changes:

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

Conclusion

By following the steps above, you should be able to resolve the .NET 5 pipeline build issues in Azure DevOps effectively. Updating your NuGet version and switching to dotnet build will minimize compatibility issues and enable a smooth development workflow. Remember that keeping your tools updated is paramount to avoid such bottlenecks in your continuous integration processes.

Now that you've tackled the common issues that prevent .NET 5 projects from building successfully in Azure Pipelines, you're ready to push forward with your development! Happy coding!