msm - merge module and vs redistribuatble behavior...

Question

0.00/5 (No votes)

See more:

Hello all
I am having an issue with the Microsoft's merge module, the .msm files . In our application we included the merge module version MFC.msm , ATL.msm , CRT.msm , MFCLOC.msm etc 8.0.50727.762 in our setup and in our later build we included version 8.0.50727.4053 . But the relevant dlls are not updated from the older version .762 to .4053 in WinSXS folder . But the replacement of the dlls works fine if we use the vs2005redist.exe . But the difference being that the vs2005redist.exe replaces the dlls in Windows/System32 folder. I have no idea why the merge modules .msm files ,when included in the installshield , setup is not replacing the older dlls .. can anyone throw some light on this please ?

Posted 30-Aug-11 18:25pm

dharani

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

mahendren · Answer 1 · 2011-08-30T19:42:00

The behaviour of dependancies for VS changed a while ago. The newer version install side-by-side with older versions. Your application exe's and dll's will then include a manifest entry referring to the versions of MFC or ATL it requires.

To ensure that the msm is being installed, inpect the Windows\WinSXS folder, it should include all the dll's (including multiple versions of the dll's).
When you install the VS2005redist.exe, are you installing the newer version (SP1) or the older version? I suspect that the redist is older, since it should not be installing directly to System32.

So in short, later versions will not replace older versions. The main question is: does your application still run correctly? If you run depends.exe (Visual Studio Tools) and inspect the dependancies, does it show that it is bound to the new versions? In that case, there are no issues.
If your application does not run correctly, take a look here: http://msdn.microsoft.com/en-us/library/ms235342(VS.80).aspx