Hello, I would like to call some executables from my Burn bootstrapper. I think that the <ExePackage> element is only meant for executables brought as a payload, not for executables already present on the target machine. So do you also recommend to implement such a "custom-action-like" call in the CustomBA instead?
To be more specific: So far, we are using InstallShield chaining, where the "root of the chain" is a dummy MSI package that does little more than acting as root of the chain. This shall be replaced by a Burn bootstrapper, which shall uninstall the old dummy MSI and another obsolete package. We cannot do this by Major Upgrade, since it is required that the single packages remain patchable. Best regards Matthias Reuss ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
