[Breaking change]: Dropping older framework versions #31399
Labels
binary incompatible
Existing binaries may encounter a breaking change in behavior.
breaking-change
Indicates a .NET Core breaking change
🏁 Release: .NET 7
Work items for the .NET 7 release
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
Pri1
High priority, do before Pri2 and Pri3
source incompatible
Source code may encounter a breaking change in behavior when targeting the new version.
Description
Starting with .NET 7 Preview 1, installing the core libraries packages into projects whose target framework is older than the following, is no longer supported:
Version
Other (please put exact version in description textbox)
Previous behavior
The latest non-prerelease core libraries packages which are part of the ".NET 6" wave are supported when used from a project targeting .NET Framework 4.6.1, .NET Core 3.1, or .NET Standard 2.0 or above.
New behavior
.NET 7 core libraries packages are supported to be used by projects targeting .NET Framework 4.6.2, .NET 6, .NET Standard 2.0 or newer.
Type of breaking change
Reason for change
Dropping a framework from a package is a source breaking change. At the same time, continuing to build for all frameworks we ever shipped increases the complexity and size of a package.
Starting with .NET 7, we no longer support frameworks which we previously supported but are now out-of-support:
Recommended action
If your project is no longer being evolved but only maintained, simply don't upgrade the impacted packages. If your project is actively evolved, upgrade it to a later framework version to one of the following:
Feature area
Core .NET libraries
Affected APIs
These packages no longer ship old frameworks:
The text was updated successfully, but these errors were encountered: