Update TFM version compatibility behavior to correctly handle CsWinRT 3.0 .1 TFMs#7287
Open
manodasanW wants to merge 2 commits intoNuGet:devfrom
Open
Update TFM version compatibility behavior to correctly handle CsWinRT 3.0 .1 TFMs#7287manodasanW wants to merge 2 commits intoNuGet:devfrom
manodasanW wants to merge 2 commits intoNuGet:devfrom
Conversation
… CsWinRT 3.0 .1 TFMs
dotnet-policy-service
Bot
added
the
Community
zivkan
reviewed
Apr 17, 2026
Co-authored-by: Andy Zivkovic <[email protected]>
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
2 participants
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.
Bug
Fixes: NuGet/Home#14859
Description
Updating the TFM version compatibility checker to correctly handle the new .1 Windows OS version TFMs that were added in .NET 10. In .NET 10,
net10.0-windows10.0.17763.1and similar TFMs for the other Windows OS versions were added to allow multi-targeting betweenCsWinRT 3.0andCsWinRT 2.xWinRT projections and not be a breaking change allowing for consumers to adopt at their own pace. But this means the version compatibility checker needs to treat the .1 revision as not compatible with .0 revision and vice-versa.PR Checklist