1
0
mirror of synced 2025-12-25 02:14:57 -05:00

Add end of support tooling policy (#9436)

* Add end of support tooling policy

* Apply suggestions from code review

Co-authored-by: Rich Lander <rlander@microsoft.com>

* Update release-policies.md

Co-authored-by: Maira Wenzel <mairaw@microsoft.com>

* Apply suggestions from code review

Co-authored-by: Maira Wenzel <mairaw@microsoft.com>

---------

Co-authored-by: Rich Lander <rlander@microsoft.com>
Co-authored-by: Maira Wenzel <mairaw@microsoft.com>
Co-authored-by: Chet Husk <baronfel@users.noreply.github.com>
This commit is contained in:
Marc Paine
2024-07-31 11:52:22 -07:00
committed by GitHub
parent 62bf6fd4d3
commit 0d223e9c87

View File

@@ -47,6 +47,16 @@ As the end of support nears for a given .NET version, we strongly recommend you
Support ends for a given .NET version when its published end of support date has passed. Support typically ends on a patch day. If there is a critical issue for that .NET version, it will be patched for the last time on that day. There will not be any patches after that point. Continuing to use an unsupported version will expose you to security vulnerabilities.
### Tooling
The month after a .NET version goes out of support, we mark that version as optional and out of support in Visual Studio. Customers can remove it from their Visual Studio installs by using the [remove out of support components](https://devblogs.microsoft.com/visualstudio/removing-out-of-support-components-from-your-visual-studio-installations/) experience.
Additionally, customers targeting an out-of-support .NET version in their projects will get a notification in Visual Studio.
6 months after a .NET version goes out of support, newer in-support .NET SDK versions are updated to produce warning [NETSDK1138: The target framework is out of support](https://learn.microsoft.com/dotnet/core/tools/sdk-errors/netsdk1138) when targeting the out-of-support version.
### Packages
[.NET packages](https://www.nuget.org/profiles/dotnetframework) are no longer supported when either of the following occurs:
- A new version of the package is available. Some packages support multiple patches versions at once, one per major version matching a supported major .NET version.