fix(vs): Use single TFM build feature from VS (backport #19440) #19445
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
(cherry picked from commit e9b7e8d)
github-actions
bot
added
the
area/build
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.
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Removes workaround used to build a single target framework by rewriting the TFMs, instead use the ootb feature from VS. This also fixes multi-TFMs issues with
ENC1002: Cannot apply changes -- unexpected error: 'Object reference not set to an instance of an object.'Fixes #19433, fixes https://github.com/unoplatform/uno.hotdesign/issues/3290
This is an automatic backport of pull request #19440 done by [Mergify](https://mergify.com).