I actually figured out the issue. The VC++ MSM files on our old build server are newer than the MSM files on the build server to which I was moved and was causing our 5.0 to 5.1 installers to run into an issue where the newer installers had older MSMs integrated and caused versioning issues. The MSI would remove the VC++ files but not put the new ones down because they were older. Thanks for the response!
-- -a "I wonder if procrastinators realize that they're not putting off work, just putting it off onto other people?" On Jan 14, 2012, at 10:35 PM, Bob Arnson wrote: > On 13-Jan-12 12:20, Schley Andrew Kutz wrote: >> My WiX installer removes the VC10 redistributable merge modules on upgrade. > > Merge modules aren't atomic; their contents are mixed into the .msi. In > this case, you're running into a known bug in MSI in how it deals with > assemblies: > http://blogs.msdn.com/b/astebner/archive/2007/02/08/assemblies-may-be-missing-from-the-gac-or-winsxs-cache-after-an-msi-major-upgrade.aspx. > > -- > sig://boB > http://joyofsetup.com/ > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Mar 27 - Feb 2 > Save $400 by Jan. 27 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
