Rob's advice was to use a "Related Bundle" , which would involve creating a bundle.exe for each "addon", and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596883.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
