Measurement Studio .NET Merge Modules

Measurement Studio 2012 for Visual Studio 2010 Help

Edition Date: August 2012

Part Number: 372636F-01

»View Product Info
Download Help (Windows Only)

See Also


Using merge module deployment for Measurement Studio applications is a multi-step process. Review each step carefully to ensure successful deployment:

Step 1: Determine the Files You Need to Include

Use the following table to determine the necessary merge modules for your Measurement Studio Windows .NET application.

Note: 64-bit merge modules are located in the same location as 32-bit merge modules; however, 64-bit merge modules have slightly different file names. For example, the 32-bit .msm for the Measurement Studio Common library is MStudioCommon.2010.msm, but the 64-bit merge module is MStudioCommon.2010_x64.msm. For Any CPU (AnyCPU in Visual Basic) applications, you must ensure that you choose the *_x64 version of the .msm when deploying to a 64-bit operating system or choose the normal x86 version of the .msm when deploying to a 32-bit operating system.
Measurement Studio Assembly Measurement Studio Merge Module Microsoft Visual Studio-Dependent Merge Modules
32-bit 64-bit
NationalInstruments.Analysis.Enterprise mkl.msm
MStudioEnterpriseAnalysis.2010.msm
nianlys.msm
niMetaUtils.msm
MStudioCommon.2010.msm
mkl64.msm
MStudioEnterpriseAnalysis.2010_x64.msm
nianlys_x64.msm
niMetaUtils.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Analysis.Professional mkl.msm
MStudioProfessionalAnalysis.2010.msm
nianlys.msm
niMetaUtils.msm
MStudioCommon.2010.msm
mkl64.msm
MStudioProfessionalAnalysis.2010_x64.msm
nianlys_x64.msm
niMetaUtils.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Analysis.Standard mkl.msm
MStudioStandardAnalysis.2010.msm
nianlys.msm
niMetaUtils.msm
MStudioCommon.2010.msm
mkl64.msm
MStudioStandardAnalysis.2010_x64.msm
nianlys_x64.msm
niMetaUtils.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Controls MStudioControls.2010.msm
MStudioCommon.2010.msm
MStudioControls.2010_x64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Controls.Booleans MStudioControls.2010.msm
MStudioControlsBooleans.2010.msm
MStudioCommon.2010.msm
MStudioControls.2010_x64.msm
MStudioControlsBooleans.2010_x64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Controls.Graphs MStudioControls.2010.msm
MStudioControlsGraphs.2010.msm
MStudioCommon.2010.msm
MStudioControls.2010_x64.msm
MStudioControlsGraphs.2010_x64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Controls.Numerics MStudioControls.2010.msm
MStudioControlsNumerics.2010.msm
MStudioCommon.2010.msm
MStudioControls.2010_x64.msm
MStudioControlsNumerics.2010_x64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Common MStudioCommon.2010.msm MStudioCommon.2010_x64.msm Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.Net CWUI_OCX.msm
DataSocketCore.msm
DataSocketServer.msm
logos.msm
MStudioNet.2010.msm
ninetbrw.msm
NIMesaDLL.msm
niMetaUtils.msm
NIMSVC_CRT71.msm
NIMSVC_MFC71.msm
NIMSVC_STL71.msm
ni_utility.msm
opcenum.msm
MStudioCommon.2010.msm
Comcat.msm
Comctl32.msm
Comdlg32.msm
HTML WinHelp.msm
Mfc42.msm
Mscomctl.msm
Msvbvm60.msm
Msvcp60.msm
Msvcrt.msm
oleaut32.msm
Microsoft_VC90_CRT_x86.msm
Microsoft_VC90_MFC_x86.msm
Microsoft_VC100_CRT_x86.msm 
NationalInstruments.NetworkVariable logos.msm
MStudioNetworkVariable.2010.msm
niMetaUtils.msm
NIMSVC_CRT71.msm
NIMSVC_STL71.msm
ninetv.msm
MStudioCommon.2010.msm
logos64.msm
MStudioNetworkVariable.2010_x64.msm
niMetaUtils.msm
NIMSVC_CRT71.msm
NIMSVC_STL71.msm
ninetv_x64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.TDMS cvitdms.msm
MStudioTdms.2010.msm
niMetaUtils.msm
tdms.msm
MStudioCommon.2010.msm
cvitdms_x64.msm
MStudioTdms.2010_x64.msm
niMetaUtils.msm
tdms64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.UI MStudioUIDesign.2010.msm
MStudioUI.2010.msm
NIMesaDLL.msm
niMetaUtils.msm
MStudioCommon.2010.msm
MStudioUIDesign.2010_x64.msm
MStudioUI.2010_x64.msm
NIMesaDLL.msm
niMetaUtils.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_ATL_x86.msm
Microsoft_VC100_CRT_x86.msm
Microsoft_VC90_CRT_x86.msm
Microsoft_VC90_MFC_x86.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)
NationalInstruments.UI.WindowsForms MStudioUIWinForms.2010.msm
MStudioCommon.2010.msm
MStudioUIWinForms.2010_x64.msm
MStudioCommon.2010_x64.msm
Microsoft_VC100_CRT_x86.msm (32-bit)
Microsoft_VC100_CRT_x64.msm (64-bit)

Step 2: Locate the Files You Need to Include

Use the following table to locate the necessary files to include when deploying your Measurement Studio Windows Forms, Windows Presentation Foundation (WPF), or Web Forms .NET application.

If you include the Intel Math Kernel Library merge module (mkl.msm or mkl64.msm) or the Mesa 3D merge module (NIMesaDLL.msm) files, you need to also include their respective license agreements and/or notices. Refer to <National Instruments>\_Legal Information.txt for information on where to find the license agreements and/or notices to include for each third-party component.

Measurement Studio and Microsoft Visual Studio-Dependent Merge Modules Location
MStudioEnterpriseAnalysis.2010.msm For 32-bit operating systems: Program Files\Common Files\Merge Modules
MStudioProfessionalAnalysis.2010.msm
MStudioStandardAnalysis.2010.msm
mkl.msm
nianlys.msm
MStudioCommon.2010.msm
MStudioControls.2010.msm
MStudioControlsBooleans.2010.msm
MStudioControlsGraphs.2010.msm
MStudioControlsNumerics.2010.msm
MStudioNet.2010.msm
DataSocketCore.msm
DataSocketServer.msm
CWUI_OCX.msm
logos.msm
ninetbrw.msm
NIMesaDLL.msm
NIMSVC_MFC71.msm
ni_utility.msm
opcenum.msm
MStudioNetworkVariable.2010.msm
ninetv.msm
cvitdms.msm
MStudioTdms.2010.msm
tdms.msm
MStudioUIDesign.2010.msm
MStudioUI.2010.msm
MStudioUIWinForms.2010.msm
Microsoft_VC100_CRT_x86.msm (Microsoft Visual-Studio Dependent)
MStudioEnterpriseAnalysis.2010_x64.msm For 64-bit operating systems: Program Files (x86)\Common Files\Merge Modules
MStudioProfessionalAnalysis.2010_x64.msm
MStudioStandardAnalysis.2010_x64.msm
mkl64.msm
nianlys_x64.msm
MStudioCommon.2010_x64.msm
MStudioControls.2010_x64.msm
MStudioControlsBooleans.2010_x64.msm
MStudioControlsGraphs.2010_x64.msm
MStudioControlsNumerics.2010_x64.msm
MStudioNetworkVariable.2010_x64.msm
logos64.msm
ninetv_x64.msm
cvitdms_x64.msm
MStudioTdms.2010_x64.msm
tdms64.msm
MStudioUIDesign.2010_x64.msm
MStudioUI.2010_x64.msm
MStudioUIWinForms.2010_x64.msm
Microsoft_VC100_CRT_x64.msm (Microsoft Visual-Studio Dependent)
niMetaUtils.msm 32-bit operating systems: Program Files\Common Files\Merge Modules

64-bit operating systems: Program Files (x86)\Common Files\Merge Modules
NIMesaDLL.msm
NIMSVC_CRT71.msm
NIMSVC_STL71.msm
Comcat.msm (Microsoft Visual Studio-Dependent)
Comctl32.msm (Microsoft Visual Studio-Dependent)
Comdlg32.msm (Microsoft Visual Studio-Dependent)
HTML WinHelp.msm (Microsoft Visual Studio-Dependent)
Mfc42.msm (Microsoft Visual Studio-Dependent)
Mscomctl.msm (Microsoft Visual Studio-Dependent)
Msvbvm60.msm (Microsoft Visual Studio-Dependent)
Msvcp60.msm (Microsoft Visual Studio-Dependent)
Msvcrt.msm (Microsoft Visual Studio-Dependent)
oleaut32.msm (Microsoft Visual Studio-Dependent)
Microsoft_VC100_ATL_x86.msm (Microsoft Visual-Studio Dependent)
Microsoft_VC100_ATL_x86.msm
Microsoft_VC90_CRT_x86.msm (Microsoft Visual-Studio Dependent)
Microsoft_VC90_MFC_x86.msm (Microsoft Visual-Studio Dependent)

Step 3: Locate Device Drivers

The following assemblies requires a device driver that is located on the National Instruments Device Drivers DVD included with Measurement Studio. Alternatively, refer to NI Drivers and Updates on ni.com and enter Device Drivers into the search field to download the latest version of the NI Device Drivers:

Step 4: Review Special Considerations for DataSocket, 3D Styles, NI-VISA, niMetaUtils.msm, ninetv.msm, mkl64.msm, logos64.msm, tdms64.msm, and Analysis .NET Class Libraries

If your application includes DataSocket, 3D Styles, NI-VISA, niMetaUtils.msm, ninetv.msm, mkl64.msm, logos64.msm, tdms64.msm, or Analysis .NET Class Libraries, review the following sections.

DataSocket

When you deploy a Measurement Studio application for Windows Vista that includes DataSocket, the end user must select Everyone in the installation instead of Just Me. You can disable the Just Me option in the installer by completing the following steps:

  1. Click your Setup Project in the Solution Explorer to view the Setup Project Properties Window.
  2. In the Properties Window, set InstallAllUsers to True.
  3. Click the User Interface Editor button in the Solution Explorer.
  4. Select Install»Start»Installation Folder.
  5. Right-click Installation Folder and select Properties Window.
  6. In the Properties Window, set InstallAllUsersVisible to False.

DataSocket does not support 64-bit applications.

3D Styles

The merge modules Microsoft_VC100_ATL_x86.msm, Microsoft_VC100_CRT_x86.msm, Microsoft_VC90_CRT_x86.msm, and Microsoft_VC90_MFC_x86.msm are only necessary if your application uses 3D styles.

NI-VISA

You need a valid NI-VISA license to use NI-VISA for application development or deployment. Measurement Studio includes a development license for NI-VISA. Examples of other products that include NI-VISA are LabVIEW, LabWindows/CVI, TestStand, NI-488.2, GPIB controllers, and PXI controllers. If you are not using any NI software or hardware, you can purchase the NI-VISA Development Software separately. Refer to NI-VISA licensing at http://www.ni.com/visa/license.htm for more information.

niMetaUtils.msm

Any deployment project that contains the niMetaUtils.msm merge module must include a SystemFolder entry and a ProgramFilesFolder entry in the Directory Table. To include this entry in Visual Studio, add a "System Folder" and a "Program Files Folder" as a Special Folder in the File System view of the deployment project.

ninetv.msm

Building a setup project with ninetv.msm results in warnings of the following type: Two or more objects have the same target location 'location'. You can continue to use your setup project normally; these warnings do not affect your project, and you can safely ignore them.

mkl64.msm, logos64.msm, and tdms64.msm

Visual Studio does not add these merge modules when building x64 projects. You must manually add these .msm files to your project.

See Also

WAS THIS ARTICLE HELPFUL?

Not Helpful