![]() ![]() The solution was very simple, once figuring out what the culprit was. ![]() T16:11:54.8883410Z Found tool in cache: NuGet 4.1.0 圆4 Solution: Create a "NuGet Tool Installer" task When I examined the logs of the pipeline execution, I noticed that it didn't use the latest version and it tried to fetch version 4.1.0 from the cache: T16:11:54.8393379Z Caching tool: NuGet 4.1.0 圆4 This struck me as odd, as I know for a fact that a lot of the packages I use that got this error message indeed have support for the latest incarnation of dotnet core. It clearly states that One or more packages are incompatible with. One or more packages are incompatible with. Package .Contracts 2.0.1 supports: netstandard2.0 (.NETStandard,Version=v2.0) Package .Contracts 2.0.1 is not compatible with netcoreapp2.1 (.NETCoreApp,Version=v2.1). Package 2.0.0 supports: netstandard2.0 (.NETStandard,Version=v2.0) Package 2.0.0 is not compatible with netcoreapp2.1 (.NETCoreApp,Version=v2.1). If you're using Azure DevOps (also known as VSTS), and you work with dotnet core in any capacity, perhaps you're migrating from one version to the next - as I was for some of my projects.Īn error that struck me was the following (redacted for clarity and brevity in the post): Errors in D:\a\1\s\\\ □ TIP: Check out the guidance for building sustainable Azure workloads! □
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |