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
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
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
t automatically uninstalled if the Bundle is uninstalled)?
>
> -Original Message-
> From: nianderneves [mailto:niander.ne...@gmail.com]
> Sent: June 27, 2013 15:10
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Creating separate entries in Add/Remove for
...@gmail.com]
Sent: June 27, 2013 15:10
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating separate entries in Add/Remove for each MSI in a
bundle
Hello,
Can I generate separate entries in Add/Remove for each MSI that my bundle
installs?
The bundle just put a reference for him in
Hello,
Can I generate separate entries in Add/Remove for each MSI that my bundle
installs?
The bundle just put a reference for him in Add/Remove.
I want that my bundle put a a reference for him in Add/Remove and also a
reference for each MSI that the bundle instaled. The bundle would give the
opt
6 matches
Mail list logo
