Add platform moniker to workload pack MSI #11578
Merged
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.
We should always add the platform moniker to the generated workload pack MSI. We previously avoided this if the package for the workload pack contained the platform to avoid repeating platform information multiple times.
However, when using aliasing, e.g. taking an x64 pack and repurposing it for arm64, etc. we now end up with duplicate file names that results in conflicts when generating the visual studio manifests.
For example, a manifest like
would generate a single MSI named
Microsoft.AOT.win-x64.Cross.android-arm64.6.0.11-mauiarm.msi. With this change, we'll generate two MSIs instead.Microsoft.AOT.win-x64.Cross.android-arm64.6.0.11-mauiarm-arm64.msi
Microsoft.AOT.win-x64.Cross.android-arm64.6.0.11-mauiarm-x64.msi