While I am not clear on what you want to do, this thread may help: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-Burn-driven-installer-in-quiet-mode-command-line-parameters-td5913001.html
If you are writing the BA you can get the command line and then set a variable, which you then use in the ExePackage/@InstallCondition. If you are using the WixStdBA, I am not sure how to detect that -quiet switch was provided when the bundle was launched. In 3.8 you could use a BAFunction, or in 3.7 use the WixExtenededBootstrapper. Or you could create an overwritable variable and also pass it on the commandline when doing quiet mode. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ExePackage-and-Quiet-install-condition-tp7588075p7588105.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
