My approach to the problem is to just detect the problem during installation and inform the user about it. If there are files found on the target folder after the previous version should have been uninstalled (after RemoveExistingProducts step) then abort the installation. More details: http://stackoverflow.com/q/13683651/395718
Bootstrapper is not required for this. Derek Wickern wrote > I need to upgrade a package which was unfortunately created with > per-user scope. It's installing to ProgramFiles. I understand that MSI > can't upgrade my perUser to perMachine. > > I have some ideas: > 1. Automatically uninstall the per-user package (custom action?) > 2. Install the per-machine package right on top of the per-user package > 3. Detect the scope of the original package and upgrade to the same > scope. Otherwise default to perMachine. > > I just upgraded my project to WiX 3.6 and I'm using burn to create a > boostrapper. I'm hoping that gives me more options. > > What's the best solution here? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-6-upgrading-perUser-to-perMachine-tp7582131p7582460.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
