For looking at this in the future reference I should add that original post was deleted because I discovered that I was delusional when I wrote "Bundle Command line not passed to second MSI package". An errant line of code was causing the specific behavior that one MSI had LOGVERBOSE set and the others did not have it set.
Tanu, you probably should start a new thread with your new concerns. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-users-f687560.html It sounds like you are describing the intended wix design. Since burn.exe is more than just a bootstrapper and owns the MSI which it launched for the life of the installation, I would expect all of the threads to be killed when the parent process is killed. Burn is not designed to 'launch-and-forget'. I expect others can explain this better than I. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Bundle-Command-line-not-passed-to-second-MSI-package-tp7593291p7593311.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
