.NET December 2022 Updates – .NET 7.0.1, .NET 6.0.12, .NET Core 3.1.32
Today, we are releasing the .NET December 2022 Updates. These updates contain security and non-security improvements. Your app may be vulnerable if you have not deployed a recent .NET update.
You can download 7.0.1, 6.0.12, and 3.1.32 versions for Windows, macOS, and Linux, for x86, x64, Arm32, and Arm64.
- Installers and binaries: 7.0.1 | 6.0.12 | 3.1.32
- Release notes: 7.0.1 | 6.0.12 | 3.1.32
- Container images
- Linux packages: 7.0.1 | 6.0.12 | 3.1.32
- Release feedback/issue
- Known issues: 7.0 | 6.0 | 3.1
Improvements
- ASP.NET Core: 7.0.1 | 6.0.12 | 3.1.32
- Installer: 7.0.1
- SDK: 7.0.1 | 6.0.12
- Runtime: 7.0.1 | 6.0.12
- Templating: 7.0.1
- Winforms: 7.0.1
Security
CVE-2022-41089 – .NET Remote Code Execution Vulnerability
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 3.1, .NET 6.0., and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A remote code execution vulnerability exists in .NET Core 3.1, .NET 6.0, and .NET 7.0, where a malicious actor could cause a user to run arbitrary code as a result of parsing maliciously crafted xps files.
Visual Studio
See release notes for Visual Studio compatibility for .NET 7.0, .NET 6.0 and .NET Core 3.1.
.NET Core 3.1 End of life
.NET Core 3.1 will reach end of life on December 13, 2022, as described in .NET Releases and per .NET Release Policies. After that time, .NET Core 3.1 patch updates will no longer be provided. We recommend that you move any .NET Core 3.1 applications and environments to .NET 6.0. It’ll be an easy upgrade in most cases. The .NET Releases page is the best place to look for release lifecycle information. Knowing key dates helps you make informed decisions about when to upgrade or make other changes to your software and computing environment.
Light
Dark
3 comments
Starting from today Visual Studio 2019 now cannot target any .NET version in a supported way. All 3 related workloads are not officially supported anymore:
1) .NET cross-platform development workload (.NET Core 3.1 and .NET 5.0 is not supported anymore)
2) ASP .NET and web development workload (ASP .NET Core 3.1 and ASP .NET Core 5.0 is not supported anymore)
3) Data storage and processing workload (Entity Framework Core 3.1 and Entity Framework Core 5.0 is not supported anymore – even EF Core 3.1 on .NET Framework 4.8 is not supported)>
So the only options left (for companies that are unable to upgrade to Visual Studio 2022 and .NET 6.0 in nearest future) are downgrade to .NET Framework 4.8 (with losing cross-platform then), ASP .NET Core 2.1 on .NET Framework and classic Entity Framework 6.4.4. Ironically all that outdated technologies are still supported. But that is a big step backwards (language syntax, class library, performance, etc.).
.NET cross-platform development was one of the main benefits for Visual Studio 2019 over Visual Studio 2017. But today almost all of them has become unsupported and Visual Studio 2019 reaches feature parity with Visual Studio 2017 in that case. Visual Studio 2019 is in a Mainstream Support phase till April 2024 as opposed to Visual Studio 2017 with Mainstream Support ended April 2022 – so that looks very strange and disappointing.
I’ve asked about this situation on Github – still no reply from Microsoft for more than 2 month..
Hi. I just looked in my registry and my latest version of .NET seems to be 4.8.04084 (and this was with my latest windows 10 update). So I am confused when you say the latest version is 7.0 as this seems a loooong way off what I have. (sorry, I am not a programmer, so I may be confusing myself here)
They are different products, .net framework and .net