>>> John said: For my own work, I am creating a managed bootstrapper to handle my previous collection of features as individual MSI's property-driven by the UI of the bootstrapper. IMHO, this is the way to go.
I agree that this approach is the way to go! A separate msi for each "feature" (or sub-feature) of the IS project and then let Burn select which MSI to install based on user selection. Also agree that an mba is definitely the way to go, but you can also do this using WixStdBA and bafunctions.dll. Search this list for examples or look at examples at https://wixextba.codeplex.com/ (although the code there is now part of wix 3.8 or later). -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdBA-Does-not-allow-to-modify-the-chained-msi-features-in-maintenance-mode-tp7598178p7598182.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
