>From the original post, the requirement is to down-version installed files and avoid the bug that GAC and SxS assemblies are missing, So RemoveExistingProducts must be before CostInitialize, the placement that is not documented but seems ok according to my support call of a few years ago. None of the documented locations for REP work for the problem, hence the comment in the original post about doing it before CostInitialize.
Applying the hot fix might work, but it's my understanding that it cannot be redistributed and therefore you must ask the customer to evaluate and install it, such is the nature of hotfixes. It's also possible that the original product may need to have been installed with the fix applied. Either way, it's not a straightforward solution to just get the upgrade done. --------------- Phil Wilson On Wed, Apr 23, 2014 at 7:45 AM, Wheeler, Blaine (DSHS/DCS) <bwhee...@dshs.wa.gov> wrote: > Can the answer be as simple as when you schedule RemoveExistingProducts? > > Bob Arnson made this post on his blog that really helped me: > http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ > It includes a link back to MSDN > http://msdn.microsoft.com/en-us/library/aa371197%28VS.85%29.aspx > > I do my very best to avoid custom actions so although it is a little slower > the default schedule RemoveExistingProducts in the <MajorUpgrade> element > works best for me. > > > -----Original Message----- > From: kirannhegde [mailto:kirann.he...@gmail.com] > Sent: Tuesday, April 22, 2014 10:41 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Major upgrade removing files > > Folks, > > Thanks for all the responses. > > This issue happens even with normal files(not just assemblies) > MSI (s) (48:F0) [07:39:21:024]: Disallowing installation of component: > {4D2EB851-13AC-500F-9704-AB78102F8D0F} since the same component with higher > versioned keyfile exists > > I dont want to implement a solution on a case by case basis. I want a > generic solution which once implemented continues to work for any file, if > that file has to be downgraded. > > Sequencing REP seems the most appropriate at the moment. > > Regards, > Kiran Hegde > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-removing-files-tp7594245p7594268.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
