.NET November 2022 Update - .NET 6.0.11 and .NET Core 3.1.31

[dcwhittaker]

.NET November 2022 Update

Release Notes

• 6.0.11
• 3.1.31

Status

Asset Type	6.0.11	3.1.31	Notes
Installers/Binaries	✅	✅
Container Images (Linux)	✅	✅
Container Images (Windows)	✅	✅
Winget Packages	✅	✅
Snaps	✅	✅
Linux Packages (Microsoft distribution)			The list below refers to the Microsoft-provisioned feeds (packages.microsoft.com) and does not in any way represent direct availability in distros (eg RHEL, Fedora).
Centos 7	✅	✅
Debian 10	✅	✅
Debian 11	✅	✅
Fedora 35	✅	✅
Fedora 36	✅	✅
OpenSUSE 15	✅	✅
Ubuntu 18.04	✅	✅
Ubuntu 20.04	✅	✅
Ubuntu 22.04	✅

Issues

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

• ASP.NET Core: dotnet/aspnetcore
• Entity Framework Core: dotnet/efcore
• .NET CLI/SDK dotnet/sdk
• .NET runtime dotnet/runtime
• Winforms: dotnet/winforms
• WPF: dotnet/wpf
• NuGet: nuget/home
• Containers: dotnet/dotnet-docker
• Winget: microsoft/winget-pkgs

Known Issues

[skyfrk]

According to the download page of the .NET 6 SDK, the v6.0.403 SDK is only compatible with Visual Stuido v17.3:

Using Visual Studio? This release is only compatible with Visual Studio 2022 (v17.3). Using a different version? See .NET SDKs for Visual Studio.

Why can't we use the latest version of Visual Studio 2022 (v17.4.2) with the latest version of the .NET 6 SDK (v6.0.403)?

Context: Our dependency upgrade bot upgraded the global.json file of a directory to v6.0.403 in one of our repositories and I updated Visual Studio to v17.4.2 on my machine. Now I always have to downgrade the .NET 6 SDK while developing locally...

[dcwhittaker]

Closing in favor of #8037

[mairaw]

@skyfrk do you mind creating a separate issue for this? I can then follow-up with some folks to see if maybe the language on the site is wrong.

[skyfrk]

Where should I open the issue? In this repo? @mairaw

[mairaw]

Yes, please @skyfrk