I've been at this for a few days now and it seems there is no way to create a bootstrapper that correctly launches msiexec for new installs and minor upgrades. Everyone seems to say not to use minor upgrades and instead do a major upgrade (then this wouldn't be a problem) but that is realistically not a user friendly option. First my installs install windows services which typically require domain admin credentials. Next many of my customers install to non-standard folders. So if I force a major upgrade then the users have to reset both the windows service credentials and possible keep re-pointing to their non-standard install directory. Installs are released weekly...not an option. So is my only solution InstallShield? It seems so. Please someone prove me wrong. Someone has to have tackled this problem.
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
