On 25-Aug-11 08:37, jhennessey wrote: > I've been playing with a custom UX (managed) and I've discovered that I don't > have access to some key MSI feature information in the DetectMsiFeature > handler.
Two general comments: 1. If you want something, file a feature request so it doesn't rely on e-mail being tracked.<g> 2. In general hand-wavy terms, the BA interface reflects the information Burn has, which is generally the information Burn needs to handle the chain. So Burn collects some information from the Feature table during the bind phase to let the BA turn features on/off; it doesn't collect everything from the Feature table because it doesn't need it (e.g., cost, directory). Burn lets you pass data from your bundle to a BA with the "BA manifest," which is a file created at bind time from data flagged as going into the manifest. You can see some of that in WixBalExtension; the balutil library has a bunch of helpers for reading the manifest and the .wixlib which creates the data. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
