Thanks for this information; I guess I should have mentioned one of the reason why I wanted to do this: I wanted to have this information available in the package itself. Our bundles do not always (almost never) contain MSIs; we just repackage MSUs in them, for the most part, so MsiProperty is out. I saw the bit about variables. Given the bundle, how does one get the variable out? Does running it through the Microsoft.Tools.WindowsInstallerXml.Unbinder produce it anywhere? Which file?
Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada -----Original Message----- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: April-30-14 12:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [SPAM] Re: Properties and Bundles In a burn bundle there are 'variables' (but it is not the same as a Property which is an MSI concept). You can define a variable in the bundle, and you can persist it. <Variable Name='svMsiFastValue' Value='7' Type='string' bal:Overridable='yes'/> (you can add the Persist="yes" to the above line if you want burn to do the persisting.) Note that even though I think of this value as a number, if you want to pass it to a MsiProperty, then define it as a string variable in the bundle. In your MsiPackage you can then pass the burn variable as a MsiProperty. <MsiProperty Name='MSIFASTVALUE' Value='[svMsiFastValue]'/> Back to the variable declaration because you did Overridable='yes' you can pass MSIFASTVALUE on the command line or change it in your bootstrapper application. When using the WixStdBA you can avoid the above and pass public properties in the command line of the bundle, and if it does not know about the public property it will pass it on to each MSI in the chain. Also if a user will launch your MSI without using the bundle (such as an on-demand' repair by MSI) then you will want to implement the 'remember property' pattern in your MSI. For most values that I pass to MsiProperty I make sure I implement the 'remember property' pattern in the MSI and skip using persist=yes on the burn variable. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Properties-and-Bundles-tp7594441p7594446.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
