Reputation: 8033
We just migrated our installer from WiX 2.x to WiX 3.6 and started using Burn. Previously, we were installing the Visual C++ redistributable by including the .msm files from C:\Program Files\Common Files\Merge Modules
to our MSI. Those files are always in sync with the one we use to build our product (they are updated frequently by Microsoft to include security fixes).
Now, we would like to have the Visual C++ redistributable downloaded only if required by using the Burn framework. However, Burn does not define a MsmPackage
element to place inside Chain
.
What is the best approach for deploying Visual C++ redistributable using Burn?
Upvotes: 9
Views: 3692
Reputation: 24413
This is what you should do:
Now 2) will ensure that in upgrade scenarious the MSI won't be installed, or if it is an external payload, it won't be downloaded.
The problem with packaging vcredist*.exe
is that some user might think that it is an independent install and uninstall it and break your application.
Upvotes: 1
Reputation: 21896
Merge modules can only be merged into an .msi; they can't be installed independently. You can use ExePackage
to install the appropriate vcredist*.exe.
Upvotes: 7