Problems Deploying NI components, 'Found conflicts between different versions of the same dependent assembly.'

[Hatefk]

Hello All,

This problem is kind of related to my other pending problem here. This is a VB application that I wrote several monthes ago, using VS2010 [Professional Ver 10.0.30319.1] and MS2010 [SP1 - V9.1.0.204] (this is another one not the one I asked about on the other thread!) I needed to make some minor changes and checked-out the solution from SVN. Made the changes (literaly changing some strings/titles and things like that!) and rebuilt the installer (Using the VS installer project and got these warnings. They did not exist at all before:

1 - Unable to find module dependency with signature 'Microsoft_VC100_CRT_x86.AFA96EB4_FA9F_335C_A7CB_36079407553D'

This is the exact warning that I get/mentioned on the other thread. (previously I had replaced my original Microsoft_VCXXX_.... modules with the ones that i downloaded from this website to get rid of a similar problem for microsoft modules (that had a different signiture).

2 - Found conflicts between different versions of the same dependent assembly.    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets    1578

To find the root of this problem, I looked into the 'Detected Dependencies' folder in the solution explorer window for the installer project. Here is their list:

•  Microsoft .net Framework
•  microsoft_vc100_atl_x86.msm
•  microsoft_vc100_crt_x86.msm
•  microsoft_vc90_crt_x86.msm
•  microsoft_vc90_mfc_x86.msm
•  mstudiocommon.2010.msm  *right-click->properties->dependencies:
1. MS .Net Framework
2. Microsoft_VC100_CRT_x86.AFA96EB4_FA9F_335C_A7CB_36079407553D  Version 10.0(This one shows a warning icon next to it!)

• mstudioui.2010.msm *right-click->properties->dependencies:
1. MS .Net Framework
2. microsoft_vc100_atl_x86.msm (Version 10.0 , no warning displayed!)
3. microsoft_vc100_crt_x86.msm (Version 10.0 , no warning displayed!)
4. mstudiocommon.2010.msm (Version 9.1.0.159)
5. mstudiouidesign.2010.msm (Version 9.1.0.203)
6. nimesadll.msm

• mstudiouidesign.2010.msm *right-click->properties->dependencies:
1. MS .Net Framework
• mstudiouiwinforms.2010.msm
1. MS .NET Framework
2. mstudioui.2010.msm (ver: 9.1.0.204)
• NationalInstruments.Common.dll
1. MS .Net FrameWork
2. NationalInstruments.Common.Native (Ver 12.0.40.253)
3. NationalInstruments.MStudioCLM (Ver 12.0.40.253)
4. NationalInstruments.NiLmClientDLL (Ver 12.0.40.253)

• NationalInstruments.Common.Native.dll
• NationalInstruments.MStudioCLM.dll
• NationalInstruments.NiLmClientDLL.dll
• nimesadll.msm
1. microsoft_vc90_crt_x86.msm (Ver 9.0)
2. microsoft_vc90_mfc_x86.msm (Ver 9.0)
3. nimetautils.msm
4. policy_9_0_microsoft_vc90_crt_x86.msm (Ver 9.0)
5. policy_9_0_microsoft_vc90_mfc_x86.msm (Ver 9.0)
• nimetautils.msm
• policy_9_0_microsoft_vc90_crt_x86.msm (Ver 9.0)
• policy_9_0_microsoft_vc90_mfc_x86.msm (Ver 9.0)

Therefore, to me it seems that there is a problem in one of the NI modules that uses a different version of microsoft_VC_10.... than the other Ni modules use. therefore, even if I replace the microsoft merge modules for that particular NI module, it will crash other NI modules!

Besides these two problems I get plenty of these warnings:

3 - Two or more objects have the same target location ('[payload_ul]\9.0.30729.1.policy') / Two or more objects have the same target location ('[policydir]\9.0.30729.1.cat') (I get four of each!)

This one is new and I dont know how to collect more details about it. However, I feel that if I am able to resolve the issue with verison mismatch for that MS_VC100 .... msm, this will go away. It seems that this error is arised if two objects with the same name (.dlls, icons, images , .... are being copied to the same folder when being installed. I deleted all icons, images, everything that could be copied by the installer multiple times (that was added by myself), from the project but this problem still presists! I think its trying to write two versions of the same file to the target directory and causes this warning to arise.

4 - and the lat warning (which could be unrelated to these but just happened and emerge along with these warnings: Configuration file 'C:\.....\app.config' is being used to configure all executables

This is really frustrating for me because all this program uses from NI is one LED control! because of a simple LED I have to have a long list of dependencies that may stop working any minute if either NI or VS upgrades and causing me all sort of head aches! I am trying to create my own LEDs and other controls to simplify my program as much as I can.

Right now my application does not work at all on any other computer but mine! I am really looking forward for your tips. Please let me know if I can provide more details on these.

Thanks alot in advance,

Hatef

[Hatefk]

After replacing the MS_VC100_CRT_x86/64.MSMs in my GAC folder (as per NI tech. Supp. suggestion) I still get all those errors. although now the Installer builder complains about not having MS_VC100_CRT_x86/64.MSM.DF495 ... (The ones with the signature that were already there!):

 

It seems that mstudioui.2010.msm is the only one that is looking for Microsoft_VC100_CRT....DF495.....

I tried adding the "Microsoft_VC100_CRT....DF495....."to the installer project but still no luck 😞

Any idea? Has anyone faced this issue?

Is there a way to avoid this type of problem in the future at all?

[Hatefk]

Here is more detail about the dlls and msm used in my app.

As a test app., I created a new visual studio VC# project for .Net 4.

Added 3 LEDs to the main form.

Added an installer project to the solution.

Added the main output of the test project to the installer project and then there are several NI .msm's and .dll's added to the detected dependencies folder.

their list exactly equals to what I mentioned in my original post, only this one has differed:

1. MStudioUICommon.2010.3DAB91FED19D4807AC84E31805C87270
1. Microsot .NET Framework
2. microsoft_vc100_atl_x86.msm
3. Microsoft_VC100_CRT_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
4. mstudiocommon.2010.msm (Ver 9.1.0.159)
5. mstudiouidesign.2010.msm 9.1.0.203
6. nimesadll.msm

I think somehow at some point, all the NI .msm/dlls got updated on my PC except this one (Maybe my internet connection was bad, maybe NI did not update the microsoft merge module signature in the file in that update and then I did not update my NI again, whatever,....). Therefore, he is still looking for the old Microsoft_VC100_CRT module.

If you can, please provide me with a MStudioUICommon.2010.msm that seeks the same Microsoft_VC100_CRT module as the rest of the NI modules on my PC.
So that I can try and see if replacing this will fix my problem or not!

Thanks

Hatef

[NomeAlternativoVeramente]

I got same problem. Just added a "led" to my project and a lot of problems started. Very noisy 8 warnings because of some target file that will have same location...

The worst part is that a collections of simple controls just like the ones provided with Measurement Studio, are SO incompatible with our projects that they become useless. Much more better to create a "led control" from scratch using System.Drawing.

And theoretically they also want money for those .NET controls.