.NET Adapter
- Updated2025-07-23
- 2 minute(s) read
Use the .NET Adapter to call .NET assemblies written in any .NET-compliant language, such as C#
or Microsoft Visual Basic .NET. TestStand installs .NET if it is not present on your machine
during installation, which allows you to take advantage of the capabilities of the .NET
Adapter. You can configure the .NET Adapter using the .NET Adapter Configuration dialog
box.
Note You can execute .NET Framework
assemblies using .NET as long as the resources used in the .NET Framework assemblies are
present in .NET.
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 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. NI recommends that you use the sequence analyzer and
update the prototypes of .NET steps as needed when the prototypes in code modules change.
Related Information
- Code Modules
- .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
- Module Adapter Parameter Mapping Guidelines
- Platform-Specific Assemblies in 32-bit TestStand and 64-bit TestStand
- Programming with the TestStand API in Microsoft Visual Basic .NET
- TestStand Sequence Analyzer
- TestStand 2024 Q4 Changes
Learn about new features, behavior changes, and other updates in TestStand 2024 Q4.