We are building a type of 'universal installer' for a set of our products. This universal installer is a .NET app that manages a cache of MSI files located in ProgramData. Management wants to deliver the product in a MSI bundle that would install the binary as well as populate the cache with product MSIs. The problem comes in when our users try to install older versions of these "bundles". Management wants the older versions to populate the cache but not overwrite the binary in program files. We also want only one entry in add/remove for removing the entire thing.
Here's what I've tried so far: - Setting OnlyDetect='yes' for both newer and older versions on UpgradeVersion. This leaves us with multiple entries in add/remove. I tried setting ARPSYSTEMCOMPONENT=1. That prevented duplicate add/remove entries but the extra products were still installed so our reference counting was all messed up. - Setting OnlyDetect ='no' for both newer and older versions on UpgradeVersion and setting the component that installs the binary to permanent=yes. This prevents the binary from being deleted but I don't know how to eventually delete them since I don't know how to tell the difference between a remove that's being done as part of an upgrade or a remove that is being done by the user. (for example through control panel) Any thoughts on how to accomplish this? Thanks Reggie ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
