Replace the .NET Framework 4.6.1 target framework moniker by a .NET Framework 4.6.2 TFM #2179
Conversation
This file contains 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
…ramework 4.6.2 TFM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
OpenIddict currently targets .NET Framework 4.6.1, that stopped being supported two years ago. A lot of projects - including Microsoft projects - started requiring .NET Framework 4.6.2 as the lowest version. This PR adopts the same logic in OpenIddict by replacing the
net461TFM by anet462TFM.Note: most OpenIddict packages still target .NET Standard 2.0 - which means you can still use them on .NET Framework 4.6.1 - but some don't - e.g the OpenIddict OWIN packages - which will require re-targeting your application to use OpenIddict 6+.