We're using burn to create a bootstrapper app that then loads a number of applications within their own MSI's.
All of these applications have some third party shared components (ms libraries, DevX controls etc) that are installed in the GAC and will not change *very often* as they are outside of our development cycle, and so have their own msi that is installed once, rather than per application. These shared components are very large however, and therefore it would be advantageous if we could leave them on the machine during a major upgrade. If we mark the shared package as permanent, I understand that it is exactly that - the installer registers an extra system client for the component in the Windows Installer registry settings (which basically just means that at least one product is always referencing this component), so we would not be able to remove / update it if we needed to. What is the prescribed method of leaving components installed between upgrades, but still giving us the ability to remove it when we want to? Many thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Leave-components-installed-between-upgrades-but-not-permanent-tp7596436.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
