There are a few things you could consider. You could ask the other company to produce a merge module for you. There is also a custom action type for launching another MSI file, but you'll have to run it during the UI Sequence. The problem here is that there's no possibility of rollback, and you can't get at the embedded MSI file if it's wanted for anything else like repairs. The recommended method is to use a bootstrapper which installs all the pre-requisites and then installs your own product.
Rob André Pönitz wrote: > > I have a third party product with an msi based installer that I need to > install > alongside my own stuff. > > Simply launching msiexec from a custom action does not seem to work as > msiexec will complain that another installer (presumably my own) is already > running. > > Decompiling the third party installer with dark fails (dark from v3 simply > gives > up after a while, dark from v2 produces something that fails to compile > again > even with Wix v2 (and I am trying to use v3 anyway). > > The installation of the third party product should be as transparent as > possible > to the user... > > Andre' ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
