Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support statement about old target frameworks #8305

Merged
merged 1 commit into from
Feb 14, 2024
Merged

Add support statement about old target frameworks #8305

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions release-policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,8 @@ Patches are published at the [.NET Website](https://dotnet.microsoft.com/downloa

As the end of support nears for a given .NET version, we strongly recommend you move to a newer, supported version of .NET. .NET releases that have reached end of support do not get security patches. Continuing to use an unsupported version will expose you to security vulnerabilities.

End of support also applies to source that targets unsupported .NET versions. You must target a supported .NET version (via the `TargetFramework` property), for both apps and libraries. The .NET SDK produces warnings when you target out of support versions to help identify these cases. The SDK does not prevent you from targeting unsupported versions, however, your configuration will be considered unsupported.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You must target a supported .NET version (via the TargetFramework property), for both apps and libraries

This is incorrect. We specifically support targeting old TF in libraries.

Copy link
Member

@terrajobst terrajobst Mar 20, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You must target a supported .NET version (via the TargetFramework property), for both apps and libraries.

Just to add to that, we have specifically given 1P partner guidance to no waste their time upgrading .NET Framework/.NET Core versions in library projects and told them that upgrading application/services/unit tests is what they should focus on.

Also, it just doesn't make sense to say "all versions of .NET Standard are supported to target in perpetuity" and simultaneously say that targeting the frameworks that implement them from the same projects is unsupported.


## Operating System support

Each supported operating system has a lifecycle, such as the [Ubuntu lifecycle](https://ubuntu.com/about/release-cycle). The .NET team applies each of the lifecycle policies to inform adding and removing support for operating system versions. Support is typically removed when an operating system version is no longer publicly supported for free, at which point we stop testing and supporting it.
Expand Down
Loading