Re: [WiX-users] Bundle Command line not passed to second MSI package
On 08-Mar-14 17:04, Phill Hogland wrote: 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.) The Command object applies to the whole bundle; it's not package-specific. Burn automatically requests verbose logging but uses the MSI API to do so. LOGVERBOSE is a property used by WiX custom actions to determine whether they should log verbose messages. See http://www.joyofsetup.com/2008/07/15/verbose-logging-from-wcautil/. -- sig://boB http://joyofsetup.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
Re: [WiX-users] Bundle Command line not passed to second MSI package
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
[WiX-users] Bundle Command line not passed to second MSI package
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=122218951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
