My installer includes the Visual Studio 2005 SP1 merge modules.
When I do a major upgrade on Vista the VS2005 C runtime and MFC libraries
get removed. This does NOT happen when I do the same major upgrade on
Windows XP SP2.
What I found in the installer log are these two lines:
MSI (c) (F0:C0) [09:56:35:552]: skipping installation of assembly component:
{9BAE13A2-E7AF-D6C3-A01F-C8B3B9A1E18E} since the assembly already exists
MSI (c) (F0:C0) [09:56:35:567]: skipping installation of assembly component:
{98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E} since the assembly already exists
Those GUID's represent the VS2005 MFC and C runtime libraries. The messages
seem OK, since in fact the libraries are already present. The problem is
that as part of the major upgrade the libraries get removed when it
uninstalls the previous version of my product and then they never get
reinstalled.
The end result is that the application fails to run because the MFC and
runtime libraries are missing. If the user does a repair installation, the
libraries are restored and then everything is OK.
Does anyone know of any way to work around this, perhaps by modifying the
VS2005 merge modules?
--
View this message in context:
http://www.nabble.com/VS2005-merge-modules-and-major-upgrades-tf4517209.html#a12885257
Sent from the wix-users mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
