How to create a setup and deployment package that properly deploys NI DLLs - XP

[John_K]

Can you also provide examples for the UI components for 2010 (.NET Framework 4.0)?  The examples provided for the UI elements are for the 2012 versions, which I can't use and need to use the 2010 (.NET 4.0 Framework version).  Thanks!

[SerJames]

Hi John_K

Good catch, those GUID's in my example are for 2012. I will get the proper GUID's edited into the post. One thing to note is you can get the GUID's you can do this with installer developer tools such as Orca or InstedIt which are both freely available online (Orca may be installed with Visual Studio). If you open MStudioDAQmx.2010.msm in one of these tools and look at the ModuleSignature table, you will find a ModuleID, and the GUID at the end of it will be what you need, you can do the same for your 2010 components.

Here are some of the 2010 GUIDS

MStudioCommon.2010.msm: 039160C5A7A24C49AD122694436A47BB
MStudioCommon.2010_x64.msm: 561DF055CF93485F8DD042F9DE0BEEA2
MStudioDAQmx.2010.msm 7C387D31872E4A16A2BCE1ACFB96BD60
MStudioDAQmx.2010_x64.msm: B3E1E53D55AB40D9B26BF7636495762A
MStudioUI.2010.msm: 3DAB91FED19D4807AC84E31805C87270
MStudioUI.2010_x64.msm: DD4880FA34214C7B91CAC9C7ED9DB861
MStudioUIDesign.2010.msm: 957FFD52F4A5438CB870E5AC69F814E2
MStudioUIDesign.2010_x64.msm: FA8B1ACADBC6428FB1D12DA1FB460639
MStudioUI.WindowsForms.2010.msm: D8EC2CBA0684493FB9BD3BE4848569C1
MStudioUI.WindowsForms.2010_x64.msm: 357B05D45163441EBD7BA39AFBE7B484

Regards

[John_K]

Great!  I was thinking that perhaps I do NOT need to include the DAQmx DLLs.  As long as the end user installs the correct drivers from NI, and includes the '.NET Framework version 4.0" support, I think I would not need to include DAQmx in my installation program.  Correct?     At least it seemed to fix an issue I had with Visual Studio 2010 application I deployed that would crash due to the DAQmx not being installed, but it then worked if I just installed the February 2013 if I explictly included the .NET 4.0 support option.  Correct (i.e. I don't need to include DAQmx in my installer under this scenario)?

[SerJames]

That is correct, if you install DAQmx with the .NET 4.0 support you will not need the merge modules.

Regards,

[John_K]

I am making progress, but now I get the error "Error 8 Unable to open merge module 'C:\Program Files (x86)\Common Files\Merge Modules\MStudioCommon.2010.msm'. Check to make sure the module language is correct. 'The language of this installation package is not supported by your system. (Exception from HRESULT: 0x80070657)' C:\Users\kznm3l\Documents\Source\AutomatedMTITripSimulation\Setup\Setup\Common2010.wxs 18 1 Setup".  I have attached my setup project.

Any ideas?  I looked at language references (all set to "0" by NI or "1033" which is English) and culture is "en-us".  So I think everything is correct.

[SerJames]

Are you currently using that Module in another application? If you currently have the module open in Orca or InstedIt and are trying to create and build the deployment that may be causing the issue you are seeing.

Regards,

[John_K]

No, it is not open in any other application.  I will reboot, just in case.

[John_K]

I solved the problem with that error message, I needed to update all language references to 1033, as not the default value of "0".