As a setup developer, I can avoid installing prerelease versions of the wix toolset by omitting the --prerelease parameter:
dotnet.exe tool install --global wix
However, installing extensions does not yield a consistent experience. The command below installs any version, including prerelease which breaks automation.
wix.exe extension add WixToolset.UI.wixext
My solution was to pin the versions at exactly the current version which is not good.
The wix.exe extension add command supports supplying the version, but it is limited in that it does not understand pinning to major or minor versions, while letting the build increment.
For example, the following command installs v4.0.0 and not the current v4.0.4:
User story
As a setup developer, I can avoid installing prerelease versions of the wix toolset by omitting the
--prerelease
parameter:However, installing extensions does not yield a consistent experience. The command below installs any version, including prerelease which breaks automation.
My solution was to pin the versions at exactly the current version which is not good.
The
wix.exe extension add
command supports supplying the version, but it is limited in that it does not understand pinning to major or minor versions, while letting the build increment.For example, the following command installs v4.0.0 and not the current v4.0.4:
Proposal
Add the ability to avoid prerelease versions when installing extensions with
wix.exe
.Considerations
No response