.NET Adapter

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

Use the .NET Adapter to call .NET assemblies written in any .NET-compliant language, such as C# or Microsoft Visual Basic .NET. The .NET Adapter requires you to install the .NET Framework in order to take advantage of the capabilities of the .NET Adapter. Use the .NET Adapter Configuration dialog box to configure the .NET Adapter.

(Windows 10/8.1/7) When you launch Microsoft Visual Studio from TestStand, Visual Studio runs with the same privileges you used to run TestStand. If you launch TestStand while logged in as a user with standard privileges and then launch Visual Studio from TestStand, you cannot execute tasks in Visual Studio that require administrator privileges.

When you specify a module for a step, the TestStand Sequence Editor displays the .NET Module tab and TestStand User Interfaces launch the Edit .NET Call dialog box.

Note Note In versions of TestStand earlier than TestStand 2010, you could call code modules with the .NET Adapter even when the prototype in the assembly did not match the prototype you specified for the step. In TestStand 2010, the .NET Adapter and the TestStand Sequence Analyzer return an error when the prototype does not match exactly. However, for compatibility purposes, the .NET Adapter uses a similar algorithm as in previous versions of TestStand to try to run the code modules despite the error. National Instruments does not recommend relying on this behavior. National Instruments recommends that you use the sequence analyzer and update the prototypes of .NET steps as needed when the prototypes in code modules change.

See Also

.NET Code Module Support for 64-bit TestStand

Adapter and Code Module Support for 64-bit TestStand

AnyCPU Assemblies in 32-bit TestStand and 64-bit TestStand

Mapping Parameters

Platform-Specific Assemblies in 32-bit TestStand and 64-bit TestStand

Programming with the TestStand API in Microsoft Visual Basic .NET

Sharing .NET Objects Between LabVIEW and TestStand

TestStand Sequence Analyzer


Not Helpful