- Published on
- Authors
- koskila
How to avoid global.json version conflicts in Azure DevOps
In Azure DevOps, you sometimes have a project that's being built with a certain .NET version. It'll require that particular SDK version, and most typically that is defined in the global.json file. However, if you also need to install a certain .NET tool, running dotnet tool install MyBuildTool will fail. And it'll fail before it actually tries to install the version of the tool you wanted! This article explains how to work around the .



![Cover image for Azure DevOps fails with "The path [path-to-your-repo] does not exist" even though the repository is there for sure?](/cdn-cgi/image/sharpen=1,format=auto,quality=90,slow-connection-quality=50,onerror=redirect,fit=scale-down,width=1920/images/12955-bash.jpg)




















