Unable to find module

[SpringMountTech]

I'm using Meas Studio 2013 for VS2010 and having trouble building an installer for a C# program I wrote.  I've followed the instructions "Deploying Measurement Studio Applications in Microsoft Visual Studio 2010 and Earlier" (http://digital.ni.com/public.nsf/allkb/ED87C183E056CAC386256DF1004E54C6)

When I build the setup program I get several warnings:

WARNING: Unable to find module dependency with signature 'Microsoft_VC100_CRT_x86.AFA96EB4_FA9F_335C_A7CB_36079407553D'
WARNING: Unable to find module dependency with signature 'Microsoft_VC100_ATL_x86.AFA96EB4_FA9F_335C_A7CB_36079407553D'

The messages seem to be related to the Module Dependencies for mstudiocommon.2010.msm and mstudioui.2010.msm.

I have merge modules with the names 'Microsoft_VC100_CRT_x86' and 'Microsoft_VC100_ATL_x86' but they have different signatures.

I've tried reinstalling Visual Studio 2010 and Meas Studio 2013 but the files are not there.  Can someone please send these files to me or point me to another source.  Or better yet, tell me how to make measurement studo relax its requirement for this exact version of these files.  I'm not opposed to copying all required files to the installation folder on the end user's machine.

Thanks,

Bob

[PedroMunoz]

Hi Bob;

Those files can be found in C:\Program Files(x86)\Common Files\Merge Modules, or the path could change if we are talking about 64 bit. In any case. in the following document you can find the location for those merge modules:

http://zone.ni.com/reference/en-XX/help/372636F-01/mstudiowebhelp/html/netmergemodules/

[SpringMountTech]

Thanks.  I know where the common merge modules are located (I'm using 32 bit), and files named 'Microsoft_VC100_CRT_x86' and 'Microsoft_VC100_ATL_x86' are in that folder.  The problem  is that the Visual Studio installer is looking for modules with a different signature.  

Last night I reinstalled VS2010 and MS 2013 on a clean PC and now have both versions of the merge modules.  How do I get the installer to include both versions for deployement.  One of the NI DLLs in my application seems to require one version and another DLL wants the other.

Thanks,

Bob