.NET SDK 5.0.202 fails to compile netcoreapp3.1 projects

[martincostello]

Using the .NET 5.0.202 SDK to compile a project targeting netcoreapp3.1 fails with the following errors:

error NU1102: Unable to find package Microsoft.NETCore.App.Runtime.win-x64 with version (= 3.1.14)
error NU1102: Unable to find package Microsoft.WindowsDesktop.App.Runtime.win-x64 with version (= 3.1.14)
error NU1102: Unable to find package Microsoft.AspNetCore.App.Runtime.win-x64 with version (= 3.1.14)

It looks like with .NET 5.0.5 being released a week earlier than usual, it has dependencies on the 3.1 release for next Tuesday that haven't been published to NuGet.org yet.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[martincostello]

Possibly related, also having a different package restore issue on Windows builds in GitHub Actions where it fails without a NuGet.config file being present in the repo. See the following two PRs for examples.

• Update .NET SDK justeattakeaway/JustSaying#893 (error)
• Update .NET SDK to 5.0.202 justeattakeaway/JustEat.StatsD#328 (error)

[marcpopMSFT]

@jamshedd @rbhanda

[rbhanda]

Hello @martincostello , we have published 3.1.14 nugets. Please let us know if this issue is resolved after this.

[martincostello]

Yep - compilation succeeds now. Thanks!

[marcpopMSFT]

We'll close this in the morning if we hear no more reports. Thanks for reaching out.

[Shane32]

Possibly related, also having a different package restore issue on Windows builds in GitHub Actions where it fails without a NuGet.config file being present in the repo. See the following two PRs for examples.

• justeat/JustSaying#893 (error)
• justeat/JustEat.StatsD#328 (error)

I am still getting what appears to be the same nuget restore error message with GitHub Action workflows on Windows platforms. Linux platforms (same code, same workflow, same everything) runs fine.

• https://github.com/graphql-dotnet/graphql-dotnet/runs/2284168775 ( Add scoped connection builders graphql-dotnet/graphql-dotnet#2427 )
• https://github.com/graphql-dotnet/parser/runs/2282962195 ( Add support for '&' syntax token graphql-dotnet/parser#126 )

Reverting to SDK 5.0.201 corrects the error and builds properly on both platforms; you can see in the latter PR that changing the SDK version was all that was required to make it build successfully. You can also see that nuget package restore was completed successfully on Linux even though the run was canceled due to the failure on the Windows run.

[marcpopMSFT]

GitHub Actions has confirmed that they've rolled out a fix to remove an empty Nuget.config file that was still causing issues for some customers (as NuGet also made a change to not automatically include NuGet.org when an empty NuGet.config file is found). We believe this should be resolved now thought they warn that any users for the choco package manager may still be broken because that manager also creates an empty Nuget.config. Closing this issue. Please reactivate if you still see issues.