My colleague investigated some scenarios like this a few months ago. He found that when not changing the assembly version, then using the -fv switch on light and increasing the file version enabled a major upgrade of an assembly in the GAC with early RemoveExistingProducts to succeed.
Without -fv, it failed on Win2003 with MSI 4.5 but succeeded on Win7 with MSI 5. When changing the assembly version too, the major upgrade succeeded. It might be worth making a quick test installer for the scenarios you are interested in to see if you get the same results. I'd look at the GAC, rather than the log, as the indicator of what happened, to avoid misinterpreting it. -----Original Message----- From: CristianG [mailto:cristian.gherghine...@gmail.com] Sent: 30 December 2011 11:34 To: wix-users@lists.sourceforge.net Subject: [WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ? Hi, There is http://support.microsoft.com/kb/905238 a knowledge base article (mentioned also on the WiX Documentation) that describes the case of an assembly from GAC missing after a major upgrade. One of the solutions was to schedule *RemoveExistingProducts *action to occur after the *InstallFinalize *action. However, after the following test the assembly was still in GAC. The test: Using WiX 3.6, created a new setup project, with version 1.0.0.0 and *MajorUpgrade *element default, containing a dll to install into GAC. Install this small setup. Windows Installer 5.0 Create version 2.0.0.0, change Product Id (*ProductCode*) and leave the *MajorUpgrade *element default. The assembly for GAC remained the same. Checked with Orca and *RemoveExistingProducts *was scheduled after *InstallValidate * Do a major upgrade. The assembly remained in GAC. In the log file there is something like: Does that line from the log mean that the knowledge base article doesn't apply anymore ? Did I miss something and the *RemoveExistingProducts * action still needs to be scheduled after *InstallFinalize *action so that the assemblies from GAC are not removed after a major upgrade ? Thanks, Cristian -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingP roducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades- don-t-re-tp7137858p7137858.html Sent from the wix-users mailing list archive at Nabble.com. ----------------------------------------------------------------------------- - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
