|NI TestStand 2014 Help|
|NI TestStand 2014 SP1 Help|
|TestStand 2016 Help|
|TestStand 2016 SP1 Help|
|TestStand 2017 Help|
The TestStand Version Selector application indicates the active version of TestStand and can activate a different version of TestStand. 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:
The TestStand Version Selector initiates the actions described in the following table when activating a version of TestStand.
|Any||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.|
|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.|
|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.
The Current Active Version control shows the currently active version of TestStand. Select a version in the Installed TestStand versions control and click the Make Active button to activate a specific version of TestStand. The Path where 32-bit version is installed and Path where 64-bit version is installed 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.
The TestStand Version Selector supports the following command-line options:
|/?||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.|
|/noprompt||Suppresses prompts while performing activation and launch operations.|
|/reqadmin||Forces the Version Selector to require Administrator access when performing activation.|
|/installing||Displays a status prompt while activating a specified version without displaying errors. You must use this option with the /version and /noprompt options.|
|/donotreactivate||Do not reactivate TestStand if the version of TestStand is already active.|
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.