.Net Core 3.1 not yet supported in Azure Pipelines hosted agents? Getting NETSDK1045

.net-core azure-pipelines
EdH picture EdH · Dec 9, 2019 · Viewed 8.3k times · Source

It's great that .Net Core 3.1 is out, but I'm not sure the Azure Pipelines hosted agents have caught up.

My YAML pipeline specifies:

pool:
  vmImage: 'windows-latest'

and the dotnet restore step does this:

(_CheckForUnsupportedNETCoreVersion target) -> C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(127,5): error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.1. Either target .NET Core 3.0 or lower, or use a version of the .NET SDK that supports .NET Core 3.1. [D:\a\1\s\StatsNZ.BESt.DataService\StatsNZ.BESt.DataService.csproj]

works fine in .Net Core 3.0.

Are there any work-arounds, or do we have to wait for Azure DevOps to catch up?

Answer

Leo Liu-MSFT picture Leo Liu-MSFT · Dec 9, 2019

.Net Core 3.1 not yet supported in Azure Pipelines hosted agents?

No, Azure Pipelines hosted agents supports .Net Core 3.1, but the latest .net core 3.1.100 is not currently installed by default in the Azure Pipelines hosted agents.

You could check the Azure Pipelines Hosted Windows 2019 with VS2019 image, the default installed latest version of .net core is 3.0.100.

To use the .net core 3.1, you could add a Use .NET Core task to install the .net core 3.1.100:

enter image description here

enter image description here

Hope this helps.

Related questions

VSTS build: Packages failed to restore - Unable to resolve 'NETStandard.Library (>= 1.6.1)' for '.NETStandard,Version=v2.0'

I'm getting Unable to resolve 'NETStandard.Library (>= 1.6.1)' for '.NETStandard,Version=v2.0'. in VSTS build using Hosted2017 build agent after I upgraded my aspnetcore app to netcoreapp2.0 and my libraries to use netstandard2.0. Works fine locally. I've …

Read More
VSTS/Azure DevOps: Auto-Increment NuGet Package Version on Pack

Running the .NET Core Pack task, how do I get the outputted NuGet package version to auto-increment itself? So, for example, if my current version is 1.0.0, then the next time I call the Pack task, I would like to see 1.0.1. …

Read More
Build .NET Core 3.0 on Azure Pipelines

Yes, I know .NET Core 3.0 is still in preview. I would like to build this on Azure Pipelines. Is there an easy way to do this? Currently getting this error: /usr/share/dotnet/sdk/2.2.105/Sdks/Microsoft.NET.Sdk/targets/Microsoft.…

Read More