I could tell that the Command object was a single bundle instance. I had read somewhere that a mba needed to implement passing those values to a Msi and I was trying to find where to add code to add the values to the msiexec command line. In my chain I have a mixture of my MSIs and third-party MSI (and EXEs). I eventually concluded that for my MSIs I need to pass the infor into MsiProperty and use that to trigger in the Msi that I authored a SetProperty on the MsiLogging (for one example, there are others). I basically have that working, although I am still testing certain scenarios. I was trying to to turn on verbose logging (*v and not LOGVERBOSE as indicated earlier) in certain packages and not in others based on burn command-line/mba behavior. I have simplified that effort some as I tend to make a problem more complicated than is really necessary <smile/> (This is also true of MSIFASTINSTALL and of 'enabling' WIXFAILWHENDEFERRED in one of several packages, selected at run-time by the tester.)
Thanks for the feedback Bob. -- 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-tp7593291p7593293.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
