Requirements for Using .NET Framework Assemblies in LabVIEW

Whether you want to create and manipulate .NET Framework objects in LabVIEW or use LabVIEW to build .NET Framework assemblies for other applications to use, you must adhere to the following default requirements and settings.

Compatible Common Language Runtime (CLR)

To create and manipulate .NET Framework objects in LabVIEW, you must use the .NET CLR 4.0. This version of the CLR is part of the .NET Framework 4.0 that installs with LabVIEW.

LabVIEW uses the CLR 4.0 to:

  • Load assemblies —LabVIEW can load .NET Framework assemblies that target the .NET Framework CLR 4.0 or earlier. However, LabVIEW loads all assemblies in the .NET Framework CLR 4.0.
  • Build stand-alone applications, shared libraries, packed project libraries, source distributions, and ZIP files that contain VIs that use .NET Framework functions or build .NET Framework interop assemblies —LabVIEW targets these applications to the .NET Framework CLR 4.0.

Compatible Class Libraries

LabVIEW has access to the class library assemblies associated with the .NET CLR 4.0, which installs with LabVIEW. The class library assemblies of the .NET Framework determine which .NET Framework features are available to LabVIEW applications. If you build an application from a LabVIEW project or VI that relies on assemblies, the target computer for the application must have the .NET Framework 4.0 installed.

Unsupported .NET Framework Features in LabVIEW

LabVIEW supports most language features of the .NET Framework 4.0. However, .NET Framework 4.0 introduces a few new features to .NET Framework CLR that LabVIEW does not support. Refer to the KnowledgeBase at ni.com for a list of .NET Framework features that LabVIEW does not support.

Locations for Saving .NET Framework Assemblies on Disk

You must save .NET Framework assemblies that you want to call from LabVIEW in a location where LabVIEW can find them. Use the following guidelines to decide where to save assemblies.

Note NI strongly recommends that you always put VIs that use .NET Framework objects in a project.
Paths Options Loading .NET Assemblies
Tip If you encounter problems loading a particular assembly or accessing objects in an assembly, debug the assembly call or use the .NET Assemblies in Memory dialog box to verify that the correct version of the assembly is in memory.