Problems deploying NI projects using VS Installer wizard

[Hatefk]

I wrote software in VB.Net (Visual Studio 2010, Measurement studio 2010 that uses Ni-Daq modules to capture data) several months ago where I faced deployment issues. basically when trying to make the installer, I kept getting the Warning:"Unable to find module dependency with signature 'Microsoft_VC100_CRT_x86 ....'. This problem was solved quickly thanks to the solution presented HERE (which suggested downloading a differnt (older) verison of VC... merge modules for both 32-Bit and 64-Bit dlls)

However, just recently, I opened up the solution, tried rebuilding the installer again, and I get:

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

This also, causes the deployed program NOT work on the target machine. Throwing an exception about some mismatch in NI dlls. I can try reproducing it if it helps. I am not sure during these few months if the NI libraries and dlls have been updated on my computer or not and if yes, I am not sure if the version/signature of the merge modules have been modified on them.

Is there a way to verify the version of current NI-DaqMX dlls, required/correct version of MS_VC... dlls and the correct version of NI-Core Functions that needs to go on the target machine?

Please note that the numbers after 'Microsoft_VC100_CRT_x86' are not the same as the other problem. I am wondering that if I have to change the MS_VC100... merge modules again (on the development computer)?

I installed the latest version of NI Core functions for DaqMx on the target machine. Should I uninstall it and install the same version that I used to create the program?

Looking forward for your hints.

Best,

Hatef

[K_Joy]

Hi Hatef,

It seems like this is a fairly common problem, but it can be tricky to correct. The merge modules that are causing the problem are Microsoft merge modules. The NI merge modules are dependent on them (they are built against a certain version of the Microsoft modules).

It probably wouldn’t be a question of the NI libraries being updated, but rather if Visual Studio has been updated, the signature on those Microsoft merge modules may have changed.

Since it is possible that even a minor update to Visual Studio could have changed the signature on those merge modules to something other than what the dlls are looking for, it would be worth trying to replace the merge modules again and see if it corrects the problem.

Have you tried manually adding the merge modules to your installer project? What process are you using to create the installer? It might also help for us to see the mismatch exception you are getting when you run it. 

Regards,

Kelsey Johnson

Applications Engineer

[Hatefk]

Hello Kelsey and thanks for your reply.

to make sure that the merge modules are the same, I replaced what was already in my GAC folder with what I had downloaded few months ago for this same problem but it did not solve it. As I mentioned, the NI modules are now looking for a different version of Microsoft Merge Modules (the number that they are looking for is now completely different than what they were looking for back then.)

I have not tried adding those manually to the installer. (I replaced the modules in the GAC with what was suggested)

The process that I use to make the installer (which always has worked/has been working) is just to add an installer project to the main project in VS and follow those steps.

I will try to get the target computer reproduce it and post the exception message here.

But meanwhile, where can I get the microsoft merge modules that the NI is asking about?

[Hatefk]

Dear Kelsey,

Please see my other quesstion here. It contains more details on the similar problem for a different program that I wrote before.

[Hatefk · Accepted solution]

NI Tech Supp provided me with MSMs with correct signature on them. Replacing these into my GAC folder resolved the issue.

Thanks