Code modules that run in-process must match the bitness of TestStand or be bitness independent, such as an AnyCPU .NET assembly. The following table provides suggested strategies for migrating from 32-bit TestStand to 64-bit TestStand or simultaneously supporting 32-bit TestStand and 64-bit TestStand.

Adapter Code Module Type Notes
C/C++ DLL Adapter C/C++ DLL
  • DLL must match bitness of TestStand.
  • Use the $(Platform) path macro, a custom search directory that differs based on architecture, or the <TestStand Public> directory to locate the correct DLL.
LabWindows/CVI Adapter C DLL
  • DLL must match bitness of TestStand.
  • Use the $(Platform) path macro, a custom search directory that differs based on architecture, or the <TestStand Public> directory to locate the correct DLL.
.NET Adapter .NET assembly
  • Use AnyCPU assemblies when possible.
  • Assemblies that target a particular architecture must match the bitness of TestStand.
  • If you use platform-specific assemblies, use the $(Platform) path macro, a custom search directory that differs based on architecture, or the <TestStand Public> directory to locate the correct assembly.
    Note In TestStand 2023 Q4 and earlier, you can also use the GAC to locate the correct assembly.
ActiveX/COM Adapter In-process COM server
  • Server must match the bitness of TestStand.
  • TestStand automatically locates the server that matches its bitness using Microsoft Windows registry redirection.
ActiveX/COM Adapter Out-of-process COM server
  • Server does not have to match the bitness of TestStand, but TestStand uses the version that matches its bitness if that version exists.
LabVIEW Adapter VI
  • Use source-only VIs for all LabVIEW code modules to make the VIs bitness independent in most sequence files.
  • Bitness of VIs you run in-process with the LabVIEW Run-Time Engine must match the bitness of TestStand.
  • Bitness of VIs you run out-of-process does not need to match the bitness of TestStand.
  • Packed project libraries must match the bitness of the LabVIEW server you are using.
Sequence Call Adapter TestStand sequence files
  • NI recommends using bitness-independent sequences.
None Adapter N/A
  • Works the same in 32-bit TestStand and in 64-bit TestStand.
HTBasic Adapter HTBasic .prg file
  • 64-bit TestStand does not support HTBasic steps.
LabVIEW NXG Adapter N/A
  • LabVIEW NXG modules can only be used with 64-bit TestStand.
Python Adapter Python code module
  • Python version specified for use in execution must match bitness of TestStand.