.NET 5.0 will reach end of support on May 08, 2022. After the .NET May updates, Microsoft will no longer provide servicing updates, including security fixes or technical support, for .NET 5.0. You’ll need to update the version of .NET you’re using to a supported version (.NET 6.0) before this date in order to continue to receive updates.
Support Policy
.NET 5.0 is not an LTS release and is therefore supported for 18 months, or 6 months after the next release ships, whichever is longer. .NET 5.0 support will end on May 08, 2022.
When .NET 5.0 reaches end of support, applications that use this version will continue to run. That said, we won’t issue security updates for .NET 5.0 starting in May 2022 when we issue security updates for supported versions of .NET, which will be .NET Core 3.1 and .NET 6.0. This means that if a computer has .NET 5.0 installed, it may be potentially unsecure. Additionally, if you run into any issues and need technical support, we may not be able to help you.
Update your application
If you’re an end user, we recommend reaching out to the vendor managing your software to confirm whether an updated version of the software is needed and available. The remainder of this post is applicable to software vendors and developers.
If your application uses NET 5.0, we strongly recommend you migrate your application to .NET 6.0 – a supported LTS version. You can download .NET 6.0 from the .NET website.
Upgrading to .NET 6.0
In addition to the software you ship to your customers, the computer you use for development may have .NET 5.0 installed – either standalone or installed by Visual Studio.
- Open the project file (the .csproj, .vbproj, or *.fsproj file).
- Change the target framework value from net5.0 to net6.0. The target framework is defined by the or element.
- For example, change net5.0 to net6.0. You may also want to review the .NET 6 Compatibility Guide.
Update your development environment
You can check for stand-alone installations of .NET 5.0 from the command line. On a Windows computer, open a Command Prompt and go to %ProgramFiles%dotnet folder. On macOS or Linux, open a terminal window.
Then type the following command: dotnet –list-runtimes
If you use Visual Studio 2019 16.11 or 16.9 or 16.7, then based on the workloads installed, you may also have .NET 5.0 installed as a required component of Visual Studio and you need to be aware of some relevant changes that are coming.
Starting with the June 2022 servicing update for Visual Studio 2019 16.11 and Visual Studio 2019 16.9, the .NET 5.0 component in Visual Studio will be changed to out of support and optional. This means that workloads in Visual Studio may be installed without installing .NET 5.0. Note that existing installations won’t be affected and any previously installed workload and component will remain installed until the component or workload is unselected in Visual Studio setup. While it’s possible for you to re-select this optional component in Visual Studio and re-install this, we strongly recommend you use .NET 6.0 with Visual Studio 2022 to build apps that run on a supported .NET runtime.
Note: If you’re migrating an app to .NET 6.0, some breaking changes might affect you. We recommend you to go through the compatibility check.
Note: The .NET 5.0 SDK versions will continue to be supported in VS 16.11 until December of 2022 when .NET Core 3.1 goes out of support so that .NET Core 3.1 customers can continue to use 16.11 to developer their applications. This .NET 5.0 SDK will not use the .NET 5.0 runtime when running command line scenarios and will not be shipped as a stand-alone SDK.
Useful Links
Closing
.NET 5.0 will be reaching end of support on May 08 and after the .NET May 2022 updates we will no longer provide updates including security fixes, or technical support for this version. We strongly recommend you migrate your applications to .NET 6.0.
Source:
.NET 5.0 will reach End of Support on May 10, 2022 - .NET Blog
.NET 5.0 will reach end of support on May 08, 2022, this blog breaks down all the valuable information you need to know and how to update to .NET 6.0.
devblogs.microsoft.com
