Re: [WiX-users] Creating separate entries in Add/Remove for each MSI in a bundle

2013-06-28 Thread Hoover, Jacob
What would be really handy is a ba/ux with a feature tree selection driving multiple msi packages. This would need to be in addition to WixStdBA, but "getting it right" and doing it in a reusable way isn't a trivial task. Handling upgrades would be especially tricky as a bundle can't currently

Re: [WiX-users] Creating separate entries in Add/Remove for each MSI in a bundle

2013-06-28 Thread Nick Ramirez
Microsoft Office 2007 has a single entry in ARP that can be used to modify/remove the installed products. I wonder if they are using Burn to do that. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-separate-entries-in-Add-Remove-for-each-M

Re: [WiX-users] Creating separate entries in Add/Remove for each MSI in a bundle

2013-06-28 Thread Nick Ramirez
Are you installing some sort of suite of different products? Maybe the Visible flag on the MsiPackage element will get you closer to what you want. Or there might be a way to build a custom BA that would present a screen to remove particular products. -- View this message in context: http://wi

Re: [WiX-users] Creating separate entries in Add/Remove for each MSI in a bundle

2013-06-27 Thread Niander Neves de Assis
Ohh that is it! I didn't know about the Visible attribute. Thank you very much 2013/6/27 Alain Forget > If you're using Burn, wouldn't you just be able to set the MsiPackages' > Visible attribute to yes, and Permanent to yes (so that all the packages > aren't automatically uninstalled if the B

Re: [WiX-users] Creating separate entries in Add/Remove for each MSI in a bundle

2013-06-27 Thread Alain Forget
If you're using Burn, wouldn't you just be able to set the MsiPackages' Visible attribute to yes, and Permanent to yes (so that all the packages aren't automatically uninstalled if the Bundle is uninstalled)? -Original Message- From: nianderneves [mailto:niander.ne...@gmail.com] Sent: J