Does TestStand Support Using LabVIEW-generated .NET Assembly Code Modules?
Primary Software: TestStand
Primary Software Version: N/A
Primary Software Fixed Version: N/A
Secondary Software: N/A
Problem: I would like to use a LabVIEW-generated .NET Assembliy with my TestStand system. Is this supported by TestStand, and what issues and Caveats should I be aware of?
Solution: National Instruments does not recommend using LabVIEW-generated .NET assemblies to develop a TestStand system due to the following known issues:
ActiveX and .NET Object parameters are not supported in LabVIEW .NET Interop assemblies
If you use a LabVIEW interop assembly, you cannot pass activeX or .NET object parameters, such as the TestStand sequenceContext or other objects, to the assembly.
LabVIEW Runtime fails to load a LabVIEW .NET Interop assembly in a .NET 4.0 application
When calling a LabVIEW built assembly from an application targeted to the 4.0 Common language Runtime (CLR), such as TestStand 2012 or later, the assembly fails with the error:
failed to call init lv client function
This is due to a change in the 4.0 CLR where LoadLibrary is not called when loading an assembly. To prevent this issue, call LoadLibrary (in kernel32.dll) in your sequence prior to calling a function within the LabVIEW built assembly. You must also configure the load option for the step calling the LabVIEW interop assembly to load dynamically in the General section of the properties tab of the Step Settings pane.
Note: this cancause the assembly to be loaded twice in the .NET application. Be aware of this as it may have application specific side effects.
Related Links:
Attachments:
Report Date: 05/16/2014
Last Updated: 05/16/2014
Document ID: 6LFBJ8UB
