I have a bundle with an mba and several nearly identical MsiPackages (which install various printer drivers). So except for a different path to the msi the bundle MsiPackage authoring is identical for each driver package. The thing that I noticed is that when I set LOGVERBOSE on the command line of the bundle, I can see in the mba's InstallViewModel in ExecutePackageComplete that for each MsiPackage the sender.base.Command.wzCommandLine includes "LOGVERBOSE" (or whatever command line parameter I handed to my bundle.)
However only the log (and behavior) of the first MsiPackage reflects that the property was passed on the command line. The other msi package logs do not have this property on their command lines. I know that I can add a MsiPackage/@MsiProperty to package and then get the property into the MSI, but since the behavior is enable if the property exists regardless of the value, I'm trying to find a way to pass the property to the MsiPackage only if it was on the bundles command line. Any insights into this issue and how I should research it further would be appreciated! Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Command-line-not-passed-to-second-MSI-package-tp7593226.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
