.NET Core August 2020 Update - 2.1.21 and 3.1.7 #5057

rbhanda · 2020-08-11T17:42:07Z

Blog posts

Please report any issues you find with 2.1.21 or 3.1.7, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:

aspnet/Home - for ASP.NET Core questions
aspnet/EntityFrameworkCore - for Entity Framework Core questions
dotnet/cli - for CLI tools and questions
dotnet/runtime - for runtime, API, or installer issues and questions
dotnet/winforms - for Winforms issues
dotnet/wpf - for WPF issues

Status of availability of SDK on Linux feeds:

Distro	3.1.401	3.1.7	2.1.21
Ubuntu 16.04	✅	✅	✅
Ubuntu 18.04	✅	✅	✅
Ubuntu 20.04	✅	✅	✅
Centos 7	✅	✅	✅
Debian 9	✅	✅	✅
Debian 10	✅	✅	✅
Fedora 30	✅	✅	✅
Fedora 31	✅	✅	✅
Fedora 32	✅	✅	✅
OpenSUSE 15	✅	✅	✅
SLES 12	✅	✅	✅
SLES15	✅	✅	✅

Known Issues

If there are any issues with the August 2020 release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.

Snap installer for 3.1.401 SDK failure - This was resolved by rebuilding and republishing snap installer for 3.1.401.
Minimize vulnerabilities by offering service which offers simple notifications when new SDK/Runtimes are released #4822 (comment) releases-index.json was not updated on storage - This was resolved by replacing file on blog storage with GitHub file.
.NET Core August 2020 Update - 2.1.21 and 3.1.7 #5057 (comment) Release notes for 3.1.7.md contained wrong VS version for .NET Core SDK 3.1.401 - Release notes were updated to reflect .NET Core 3.1.401 support for Visual Studio 16.7
Leading and trailing whitespace in releases.json files for CVE name field - This was corrected by removing the white spaces

smokedlinq · 2020-08-11T20:06:01Z

The release notes for 3.1.7 state that it supports Visual Studio 2019 version 16.6, however when running a build on a system (Azure DevOps Hosted Agent - windows-latest) with NuGet 5.6.0, Visual Studio 2019 16.6 and .NET core SDK 3.1.401 during the restore we receive the following error:

Version 3.1.401 of the .NET Core SDK requires at least version 16.7.0 of MSBuild. The current available version of MSBuild is 16.6.0.22303. Change the .NET Core SDK specified in global.json to an older version that requires the MSBuild version currently available.

I believe Visual Studio 16.6 comes with MSBuild 16.6 and the just releases Visual Studio 16.7 comes with MSBuild 16.7.

mgroetan · 2020-08-12T12:32:07Z

Today, our Azure Devops hosted build agent builds started failing, after getting its "UseDotNet" task auto-updated from .NET Core 3.1.6's 3.1.302 SDK version to the shiny new .NET Core 3.1.7's 3.1.401 SDK version.

The reason for the problems is our need to install multiple .NET Core SDKs (as mentioned here).

For reasons beyond the scope of this issue, we're still having a need for using the .NET Core 2.2.x SDK, in addition to the .NET Core 3.1.x SDK.

We now experienced the following problems when running "NuGet restore" (5.3.1):

For a (.NET Framework 4.7.2) project using the "Microsoft.NET.Sdk.WindowsDesktop" project SDK: "C:\hostedtoolcache\windows\dotnet\sdk\2.2.103\Sdks\Microsoft.NET.Sdk.WindowsDesktop\Sdk not found. Check that a recent enough .NET Core SDK is installed and/or increase the version specified in global.json."
As this particular project SDK type seems to have been introduced in .NET Core 3.0, we were able to work around that by changing the project SDK to only "Microsoft.NET.Sdk".
For any .NET Core 3.x project:
"The nuget command failed with exit code(1) and error(C:\hostedtoolcache\windows\dotnet\sdk\2.2.103\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(137,5): error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.1. Either target .NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.1."

The latter problem could be fixed by specifically requesting the use of .NET Core SDK version 3.1.302.

I have read the release notes, but can't find anything that suggests that this parallel SDK behaviour should have changed.

In the longer term, we will OF COURSE get rid of the old .NET Core 2.2 requirement, but in the short term this prevents us from using any newer SDK version. So, all in all, not a dramatic end result, and probably not a too common scenario, but nonetheless VERY surprising.

ashkanRmk · 2020-08-13T09:49:23Z

After I upgrade my dotnet runtime to 3.1.7
I got a lot of errors like this in my all projects in vs-code:

The type 'IDictionary<,>' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.

these are my info:
`▶ dotnet --list-runtimes

Microsoft.AspNetCore.All 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
`

`▶ dotnet --list-sdks

2.2.402 [/usr/share/dotnet/sdk]
3.1.401 [/usr/share/dotnet/sdk]
`

`▶ dotnet --version

3.1.401
`

those projects can run normally. but have a lot of error in dev!
my os: linux KDE NEON 20.04

huwmanatee · 2020-08-17T09:43:59Z

On Ubuntu 20.04 dotnet pack now returns:
/usr/share/dotnet/sdk/3.1.401/Sdks/NuGet.Build.Tasks.Pack/build/NuGet.Build.Tasks.Pack.targets(198,5): error MSB4181: The "PackTask" task returned false but did not log an error.

ashkanRmk · 2020-08-19T18:53:50Z

After I upgrade my dotnet runtime to 3.1.7
I got a lot of errors like this in my all projects in vs-code:

The type 'IDictionary<,>' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.

these are my info:
`▶ dotnet --list-runtimes

Microsoft.AspNetCore.All 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
`

`▶ dotnet --list-sdks

2.2.402 [/usr/share/dotnet/sdk]
3.1.401 [/usr/share/dotnet/sdk]
`

`▶ dotnet --version

3.1.401
`

those projects can run normally. but have a lot of error in dev!
my os: linux KDE NEON 20.04

My problem was solved by installing latest version of OmniSharp manually.
because of this update break functionality of extension in vs-code.

dotnet/vscode-csharp#3951

soerendalbydk · 2020-08-24T08:47:56Z

SOLUTION FOUND: DESCRIBED IN THE BOTTOM

I have a fatal problem using 3.1.7.

I have a EF Core setup in a Class Library (DLL). When I run

dotnet ef migrations add Init --context TransferDbContext --verbose

I get the error:

It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '3.1' was not found.
  - The following frameworks were found:
	  3.1.7 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:
  - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=3.1&arch=x64&rid=win10-x64

I have struggled with this error for many hours so I will shortly describe how I made it work:

I have found a solution - or rather a cirumvention

I edited the runtimeconfig.json which resides in the ouput directory. In my case: bin\Debug\netcoreapp3.1\win-x64\<ProjectName>.runtimeconfig.json (replace <ProjectName> with the name of your project).

The field version previously contained the version number 3.1. I edited it to contain the value 3.1.7 :

	{
	  "runtimeOptions": {
		"tfm": "netcoreapp3.1",
		"framework": {
		  "name": "Microsoft.NETCore.App",
		  "version": "3.1.7"
		}
	  }
	}

And I was finally able to migrate my database.

rbhanda · 2020-09-08T17:40:31Z

closing in favor of #5170

rbhanda pinned this issue Aug 11, 2020

rbhanda mentioned this issue Aug 11, 2020

.NET Core July 2020 Update - 2.1.20 and 3.1.6 #4939

Closed

rbhanda added announcement Security labels Aug 11, 2020

dagood mentioned this issue Aug 13, 2020

Snap installer - ubuntu 20.04 - libc musl dotnet/runtime#40739

Closed

rbhanda unpinned this issue Sep 8, 2020

rbhanda closed this as completed Sep 8, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

.NET Core August 2020 Update - 2.1.21 and 3.1.7 #5057

.NET Core August 2020 Update - 2.1.21 and 3.1.7 #5057

rbhanda commented Aug 11, 2020 •

edited

Loading

smokedlinq commented Aug 11, 2020 •

edited

Loading

mgroetan commented Aug 12, 2020

ashkanRmk commented Aug 13, 2020 •

edited

Loading

huwmanatee commented Aug 17, 2020 •

edited

Loading

ashkanRmk commented Aug 19, 2020

soerendalbydk commented Aug 24, 2020 •

edited

Loading

rbhanda commented Sep 8, 2020

.NET Core August 2020 Update - 2.1.21 and 3.1.7 #5057

.NET Core August 2020 Update - 2.1.21 and 3.1.7 #5057

Comments

rbhanda commented Aug 11, 2020 • edited Loading

Known Issues

smokedlinq commented Aug 11, 2020 • edited Loading

mgroetan commented Aug 12, 2020

ashkanRmk commented Aug 13, 2020 • edited Loading

huwmanatee commented Aug 17, 2020 • edited Loading

ashkanRmk commented Aug 19, 2020

soerendalbydk commented Aug 24, 2020 • edited Loading

rbhanda commented Sep 8, 2020

rbhanda commented Aug 11, 2020 •

edited

Loading

smokedlinq commented Aug 11, 2020 •

edited

Loading

ashkanRmk commented Aug 13, 2020 •

edited

Loading

huwmanatee commented Aug 17, 2020 •

edited

Loading

soerendalbydk commented Aug 24, 2020 •

edited

Loading