[release/10.0] Use Wix5 in SharedFx/Targeting Pack .msi's#65651
Merged
Conversation
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
wtgodbe
approved these changes
Mar 4, 2026
Contributor
|
blocking vmr due to prebuilt |
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.
Backport of #65637 to release/10.0
/cc @wtgodbe
Use Wix5 in SharedFx/Targeting Pack .msi's
Build aspnetcore .msi's using Wix5
Description
During the Wix5 upgrade, we updated the bundle to build with Wx5, but not the actual SharedFx/Targeting Pack .msi's that we re-distribute. This should fix the issue.
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
Brings us in line with other .msi's built with Arcade
Verification
Packaging changes reviewed?
When servicing release/2.3