Ok, I didn't know about the MajorUpgrade element. That works great and the doc is really helpful, especially the link to Bob's blog.
Michael Am 14.06.2011 15:59, schrieb Rob Mensching: > Yes, schedule your major upgrade (RemoveExistingProduct action if you're not > using the MajorUpgrade element) before InstallInitialize. > > On Tue, Jun 14, 2011 at 6:40 AM, Michael Stoll<unwicht...@mistoll.de>wrote: > >> Hi, >> >> I have a msi created with wix, which installs and uninstalls fine. But >> if I use it as upgrade, some files are kept in the prior version. >> This happens to .NET assemblies if the version is the same as before. >> That's easy to fix. >> But what happens to unversioned files during a major upgrade? What's >> about registry keys? Is it possible to have the major upgrade behave >> exactly like uninstall, install? >> Are there some guidelines what should be payed attention to? >> >> Michael >> >> >> >> ------------------------------------------------------------------------------ >> EditLive Enterprise is the world's most technically advanced content >> authoring tool. Experience the power of Track Changes, Inline Image >> Editing and ensure content is compliant with Accessibility Checking. >> http://p.sf.net/sfu/ephox-dev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
