What is the AssemblyVersion as opposed to the AssemblyFileVersion of both assemblies? Chances are very good that if the AssemblyVersions are the same, then the strong name will also be the same which will cause you problems.
-- John Merryweather Cooper Build & Install Engineer - ESA Jack Henry & Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -----Original Message----- From: kirannhegde [mailto:kirann.he...@gmail.com] Sent: Wednesday, July 23, 2014 1:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assembly updates in the GAC using Major upgrade Hello all, I am facing a strange problem where an assembly is not upgraded in the GAC after a major upgrade. V1.0 of the msi package contains v1.0.19.0 of the assembly V1.1 of the msi package contains v1.0.21.0 of the assembly. This assembly is sourced using a merge module. When i execute v1.1 of the msi package on a system which has v1.0 already installed, the assemby is not updated. I see the following error in the log file: *skipping installation of assembly component: {C238A087-B494-48A6-B69C-5A95E2FFE56B} since the assembly already exists* Here are a few things to note: -The assembly version of the dll has changed between v1.0 and v1.1. However, the component id has not changed. This should not be an issue as in a test project, i was able to upgrade the assembly in the GAC without modifying the component code, even when the assembly versions have changed. -The MsiAssemblyName table does not contain the fileVersion attribute, as required for in-place upgrade of asssemblies. This i believe is insignificant here as the "assembly version" itself has changed. This is only required if you want to update an assembly in the GAC without modifying its assembly version -in v1.1 of the msi package, RemoveExistingProducts is sequenced after InstallFinalize. -I built my test project using Wix and was able to update the assembly in the GAC by just updating the assembly versions. The same component code was used in both the base as well as the upgraded msi. What could be wrong with my production installer? The production installer has merge modules which are very old and are still being built using Wise. Any help would be very much appreciated. Thanks, Kiran Hegde -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Assembly-updates-in-the-GAC-using-Major-upgrade-tp7596052.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
