Hi Manishshirsat,
I actually was able to do the prerequisite checking and it worked like a charm.
The part that was very odd to me was that the bundle was registering itself in
addition to my main application. So, if the user uninstalled my main
application from Add/Remove programs and then
x27;ve found, Burn is not intended to be used this way. The old
setupexe/setupbld in WiX v3.5 basically does that. I'm sure there are other
things that do this. Not a lot too it.
Burn solves the problem of creating a unified installation experience across
many installation packages.
On
I'm trying to use the Wix Standard Bootstrapper Application to install two
system prerequisites before my main application installation, which is already
compiled into an Setup.exe. How can I prevent the bundle from being registered
as a separate product. I am using the DisableModify and Disab
3 matches
Mail list logo
