TestStand Environment Reverts to Default When Launching TestStand File Diff/Merge Application

Updated Nov 9, 2018

Reported In


  • TestStand

Issue Details

I am using multiple TestStand Environments so each TestStand Environment can independently maintain its own station globals, type palettes, and customized process models.
However when I am clicking Edit -> Diff Sequence File Against option the opening window is always in default <Global> Environment. 
How can I overcome this issue?


When you are clicking on Diff Sequence File Against the TestStand File Diff/Merge application is being launched. The location of this executable if you are using 32-bit version of TestStand is normally:
'C:\Program Files (x86)\National Instruments\Shared\TestStand\FileDifferLauncher.exe'

In case you are using the 64-bit version:

'C:\Program Files\National Instruments\Shared\TestStand\FileDifferLauncher.exe'

This executable can be launched with different parameters and the Environment is one of them. By default there is no parameter value for the Environment thus the <Global> Environment is being launched. However you can define the Environment by running the application with a parameter. This parameter should be a reference to the file path of the required Environment file.

Add this to the executable shortcut:
 /env <environment path>

Additional Information

You can list the available parameters of this application using the following line in the command prompt:
"C:\Program Files (x86)\National Instruments\Shared\TestStand\FileDifferLauncher.exe" /? 


Not Helpful