NET Core build task in Azure DevOpsĪs a verification, I also added a custom. Ensure that the task you add is at the beginning, so all subsequent dotnet tasks use the version you've defined: Use. In a simple pipeline, it can look like this. NET Core: Azure DevOps build Task that defines the. NET Core SDK version to use super-easy.Īdd a new build task named Use. If you use the visual designer for building your Azure DevOps pipelines, you can define the. NET Core SDK version using a Task in the UI. Knowing this means you can ensure that your build pipeline points to the correct versions too.
You already should know the version you want to target. NET SDK that should be targeted when running the dotnet commands. If you're using Azure DevOps, you can easily define the version of the. Realizing others may run into the same, here are some quick ways that I made it work - if it can help anyone, that's great. NET Core SDK differs from the configured value when running the dotnet tools. This error can happen when the defined version of the. Check that it is installed and that the version specified in global.json (if any) matches the installed version.Ī related error message that I also see regularly together with the one above is: error MSB4236: The SDK '' specified could not be found. It can depend on what versions of the SDK you've got on your machines, either local or build agent. When working with Azure DevOps, or locally sometimes with Visual Studio, you may get the following error if there's a mismatch.
0 kommentar(er)
