Fixed multitarget exclusion preprocessing before UseTargetFrameworks script call #267
Conversation
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
This was referenced Mar 5, 2025
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.
This PR fixes an issue with our
Build-Toolkit-Componentsscript where provided parameters were not being preprocessed properly before changing the EnabledMultiTargets via theUseTargetFrameworks.ps1script.This issue resulted in the
-winuiparameter not properly adjusting the expectedExcludeMultiTargets, such as excludinguwpwhen WinUI 3 is requested. The result is that the uwp TFM is appearing in some WinUI packages, and this PR fixes the issue.