The TestStand Version Selector application indicates the active version of TestStand, can activate a different version of TestStand, and can reconfigure the currently active version. Although you can install more than one version of TestStand on a computer, only one version of TestStand can be active and can run at a time. You can launch the application in the following ways:

  • (Windows 10) Click Start»National Instruments»TestStand Version Selector.
  • Run C:\<Program Files>\National Instruments\Shared\TestStand Version Selector\TSVerSelect.exe.
The TestStand Version Selector initiates the following actions for all versions of TestStand:
  • Registers the ActiveX interfaces for the TestStand API.
  • Registers the ActiveX interfaces for the TestStand User Interface (UI) Controls.
  • Registers the TestStand API and UI Controls interop assemblies for Microsoft Visual Studio.
  • Registers various ActiveX controls, DLLs, and applications located in the <TestStand>\Components directories.
  • Adds the TestStand VIs and Functions Palette and the TestStand Controls Palette to installed versions of LabVIEW.

The TestStand Version Selector also initiates the following actions for specific versions of TestStand:

Version Activated Actions
TestStand 2021 SP1 or later Installs NI TestStand Support for Debugging Python Code, which is an extension for Visual Studio Code. This action occurs only when VS Code is already installed on the computer.

When you select TestStand 2021 SP1 or later under Installed TestStand versions, and then click either Activate or Configure, the TestStand Version Selector installs the VS Code extension. If you want to perform step into debugging of Python modules, you must complete this step to install the VS Code extension.
TestStand 4.1 or later
  • Copies API files to <National Instruments>\Shared\CVI\instr\TestStand\API for LabWindows/CVI 8.5 or later, or to <CVI>\instr\TestStand\API for LabWindows/CVI 8.1.1 or earlier.
  • Adds environment variables for the <TestStand>, <TestStand>\Bin, <TestStand Public>, and <TestStand Application Data> directories. You can use the environment variables in development environments to specify paths to files in these TestStand directories. For example, you can use these environment variables to build paths in the Additional Include Directories control in Visual Studio.
    Note   The environment variables for 64-bit TestStand end with a 64 suffix. For example, 32-bit TestStand uses the variables TestStand, TestStandBin, TestStandPublic, and TestStandAppData, and 64-bit TestStand uses the variables TestStand64, TestStandBin64, TestStandPublic64, and TestStandAppData64.
In TestStand 4.1 and later, the Current Active Version control shows the currently active version of TestStand. Select a version in the Installed TestStand versions control and click the Activate button to activate a specific version of TestStand. The Path to 32-bit version and Path to 64-bit version controls show the location of the selected version of TestStand. When activation is complete, the TestStand Version Selector indicates success or displays any warnings. Click the Launch 32-bit or Launch 64-bit button to run the sequence editor application for the active version of TestStand.
Note   The TestStand Version Selector does not normally require administrator privileges to activate a specific version of TestStand on Microsoft Windows 10. To require administrator privileges for using the TestStand Version Selector, add the /reqadmin command-line option to the selector shortcut.
TestStand 4.0.1 or earlier Adds the <TestStand>\API\CVI\ directory to the LabWindows/CVI development environment search directories for include files and instrument drivers. You must exit LabWindows/CVI before activating a new version of TestStand to ensure the changes take effect.

Command-Line Options

The TestStand Version Selector supports the following command-line options:

ArgumentDescription
/?Displays help for command-line options.
/version <versionname>Activates specified version, where <versionname> is the version of TestStand to activate.
/launch <filename>Launches the executable you specify, where <filename> is the path to the executable to launch.
/nopromptSuppresses prompts while performing activation and launch operations.
/reqadminForces the Version Selector to require Administrator access when performing activation.
/installingDisplays a status prompt while activating a specified version without displaying errors. You must use this option with the /version and /noprompt options.
/donotreactivateDo not reactivate TestStand if the version of TestStand is already active.

Log File

The TestStand Version Selector creates log files, located at <CommonAppData>\National Instruments\TestStand Version Selector, when you run the version selector to activate a version of TestStand and when you run an application that uses the TestStand Engine because the engine uses the version selector to update external environments. The log files contain details about the changes the version selector made, which might be useful when debugging issues related to changing the active version of TestStand.