|LabVIEW 2015 Help|
|LabVIEW 2016 Help|
|LabVIEW 2017 Help|
|LabVIEW 2018 Help|
|LabVIEW 2019 Help|
Complete the following steps to create a .NET control in a .NET container.
Creating and communicating with .NET objects in LabVIEW requires the .NET CLR 4.0 that installs with LabVIEW. You must use a .NET 2.0 configuration file if you want to load .NET 2.0 mixed-mode assemblies. Refer to the requirements for using .NET with LabVIEW for more information about .NET restrictions in LabVIEW.
National Instruments strongly recommends that you use .NET objects only in LabVIEW projects.
|Note If you move a VI that uses a private assembly to a different folder or machine, you either must move the associated private .NET assembly files to a subdirectory that LabVIEW can search, or you must save the files in the Global Assembly Cache (GAC). If you build a VI that uses a private assembly into a shared library or stand-alone application, LabVIEW copies the associated private .NET assembly files to the data subdirectory in the same directory as the library or application.|
Do not use the Close Reference function to close the reference to a .NET control. By leaving the reference open, you ensure that the control displays correctly until you close the VI. LabVIEW automatically closes the reference when you close the VI. This recommendation differs from how you manage a reference to a block diagram .NET object.
|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.|
|Note .NET controls automatically use the user interface execution system.|
You also can add .NET controls to the Controls palette for later use.