We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a setup developer, I can't accidentally use a WiX v4 extension with WiX v5, to avoid extensibility interface incompatibilities.
WiX v5 should reject WiX v4 extension NuGet packages (those with only a wixext4 directory).
wixext4
Naturally, this is related to #7709 and I didn't forget it and create this one anew.
WiX v4 won't outright reject WiX v5 extensions but they should show up as damaged because of the different subfolder (wixext4 -v- wixext5).
wixext5
However, it should be possible to create a single .wixext with both wixext4 and wixext5 directories with payloads to support both versions of WiX.
The text was updated successfully, but these errors were encountered:
barnson
No branches or pull requests
User story
As a setup developer, I can't accidentally use a WiX v4 extension with WiX v5, to avoid extensibility interface incompatibilities.
Proposal
WiX v5 should reject WiX v4 extension NuGet packages (those with only a
wixext4
directory).Considerations
Naturally, this is related to #7709 and I didn't forget it and create this one anew.
WiX v4 won't outright reject WiX v5 extensions but they should show up as damaged because of the different subfolder (
wixext4
-v-wixext5
).However, it should be possible to create a single .wixext with both
wixext4
andwixext5
directories with payloads to support both versions of WiX.The text was updated successfully, but these errors were encountered: