NI .NET Assemblies Needed to Deploy Applications

Use the following table to determine the necessary files to copy when deploying your NI Windows Forms or Web Forms .NET application. 

Note: FxXX refers to the version of the .NET Framework that the assembly targets (for example, Fx40 denotes an assembly that targets .NET Framework 4.0).

Note: If you copy the Intel Math Kernel Library (MKL) libraries or mesa.dll with your deployment application, you need to also copy 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.

Use the following table to locate the necessary files to copy when deploying your application.

To deploy an application that includes a device driver API, you can file copy the dependent assemblies or include a device driver runtime.  Refer to National Instruments .NET Support for more information on NI .NET APIs.  Alternately, 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.

 Note: If a separate runtime installer exists for the driver you are deploying, NI recommends you use the runtime, which ensures that you have all necessary assemblies and configuration files needed to deploy your application.

Some NI .NET assemblies use publisher policy files to redirect applications to always use the most recent version of the assembly installed on the system. However, if you use file copying to deploy an application, you cannot also deploy the policy files associated with assemblies because they must be installed to the GAC using an .exe such as GACUTIL. As a result, you must deploy an application configuration file with the copied application and assemblies to replicate the policy file behavior and redirect the deployed application to use the deployed assemblies. If you do not deploy an application configuration file and you deploy assemblies that were built with older versions of deployed assemblies (such as NationalInstruments.Common.dll), the deployed application may crash at assembly load time. Refer to How to: Create a Publisher Policy File and  Redirecting Assembly Versions for more information on how to use policy files to specify which assembly version your application targets.

• If you build a 64-bit .NET application on a 32-bit operating system, you cannot perform a file copy deployment of the application because 64-bit unmanaged dependencies are not installed on 32-bit operating systems. This also applies to applications built on a 32-bit operating system for AnyCPU without the Prefer32Bit project option set to True. To successfully deploy a 64-bit application, only copy files installed on a 64-bit operating system.
• For AnyCPU applications, you must ensure that you include 32-bit or 64-bit versions of files when deploying to a 32-bit operating system or a 64-bit operating system, respectively.
• The NI-SCOPE .NET assemblies version 1.1.1 and earlier do not support file copy deployment for 64-bit applications. All other Modular Instrument assemblies support file copy deployment for 64-bit applications.
• For .NET Framework 4.0,  NationalInstruments.DAQmx.dll and NationalInstruments.UI.Styles3D.dll assemblies are platform-specific, meaning that the installer includes 32-bit and 64-bit versions of assemblies that target the x86 and x64 platforms, respectively; however, all other NI .NET assemblies target the AnyCPU platform. If you are deploying a 32-bit application, deploy the 32-bit version of the assembly (location listed in Step 2) and if you are deploying a 64-bit application, the 64-bit version of the assembly (location listed in Step 2).