Managed code files have two independent version numbers: the AssemblyVersion and the AssemblyFileVersion. The AssemblyVersion is part of the assembly's identity. The AssemblyFileVersion is not part of the identity (as far as .NET is concerned), but is the only one of the two that Windows Installer can access (and which it uses to make upgrade determinations).
If you can change the AssemblyFileVersion then I can help you remove the registry key. -----Original Message----- From: Ana Martic [mailto:t-anm...@microsoft.com] Sent: Monday, December 07, 2009 10:03 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem with removing registry key containing version info and not removing an assembly while doing a major upgrade The key itself contains the version it looks like e.g. CLSID/GUID/1.0.0.0. A file is a keypath of that component. I also have to add that it's impossible for me to change the assembly's version. ________________________________________ From: Blair [os...@live.com] Sent: Monday, December 07, 2009 5:03 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Problem with removing registry key containing version info and not removing an assembly while doing a major upgrade Is the registry value containing the version number the keypath if its component? -----Original Message----- From: Ana Martic [mailto:t-anm...@microsoft.com] Sent: Monday, December 07, 2009 7:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem with removing registry key containing version info and not removing an assembly while doing a major upgrade Hi, While creating an installer that should do a major upgrade I firstly faced the problem that the registry key containing a version number (of the previous version) doesn't get removed. In order to make it possible that the installer of the upgrade removes it I changed the GUID of the component containing that registry key. I experienced that the component with the new GUID gets installed only if I schedule "RemoveExistingProducts" after InstallInitialize. But in order not to remove an assembly from GAC I have to schedule it after InstallFinalize. Can I find some work around for this problem so that I remove the registry key and keep the assembly? Thanks ---------------------------------------------------------------------------- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
