Stop supporting ASP.NET Core 2.3 and remove the .NET Framework 4.6.2/4.7.2, .NET Standard 2.0/2.1 and UAP TFMs - #2455
Merged
Conversation
kevinchalet
force-pushed
the
targets
branch
10 times, most recently
from
April 22, 2026 17:40
15cc202 to
9221c3f
Compare
kevinchalet
force-pushed
the
targets
branch
2 times, most recently
from
April 30, 2026 17:55
36b25a3 to
d4b86b8
Compare
…4.7.2, .NET Standard 2.0/2.1 and UAP TFMs
This was referenced May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related tickets: #2451, #2452 and #2453.
To proactively identify pain points that may result from the implementation of the changes mentioned in the 3 tickets, I decided to open this PR fairly early.
In a nutshell, this PR:
net462/net472/net48target framework monikers from all the ASP.NET Core projects/integrations, as ASP.NET Core 2.3 will no longer be supported by Microsoft after April 2027. If the proposed plan is adopted as-is, ASP.NET Core 10 will be the only supported version in OpenIddict 8.x.net462/net472/net48target framework monikers from the Entity Framework Core integration package, as Entity Framework Core 2.3 will no longer be supported by Microsoft after April 2027. If the proposed plan is adopted as-is, Entity Framework Core 10 will be the only supported version in OpenIddict 8.x.net462/net472target framework monikers from all the OpenIddict projects. If the proposed plan is adopted as-is, .NET Framework 4.8 will be the only supported version in OpenIddict 8.x. Of course, the OWIN/ASP.NET "legacy" integrations will still be fully supported, but only when targeting .NET Framework 4.8.uap10.0.17763target framework moniker from theOpenIddict.Client.SystemIntegrationpackage and theOpenIddictmetapackage. WinUI 2.x/UWP will still be supported in OpenIddict 8.x, but only on Native AOT via thenet10.0-windows10.0.17763TFM or when targetingnet48.netstandard2.0andnetstandard2.1target framework monikers from all the OpenIddict projects. If the proposed plan is adopted as-is, referencing OpenIddict 8.x packages will require targeting eithernet48ornet10.0.CryptoConfig: the entire .NET ecosystem (BCL and libraries like IdentityModel) is moving towards one-shot static methods and these methods don't support overriding the actual crypto implementation.My feeling is that the removal of the ASP.NET Core 2.3 support will only affect a very limited set of applications (I'll work with the affected teams to ensure they can move to 8.0 when it ships) but that the removal of Entity Framework Core 2.3 may be a lot more problematic, as it means we'll no longer be able to use the OpenIddict Entity Framework Core stores in .NET Framework apps, making EF 6.x (mostly a legacy thing) and MongoDB the only options working out-of-the-box.