Every time you modify the configuration files outside the TestStand environment, for example, for editing the file or for replacing it with a newer version, while an instance of TestStand Sequence Editor is open, you will not see the changes in the Sequence Editor unless these files are reloaded in the TestStand environment.
To see the desired effect, you need to close the instance of TestStand currently open and then launch it again. If you continue to work with the older instance of TestStand, the Sequence Editor will detect a change in the configuration files and will generate a pop up for Reloading the Configuration files. Since this is generated by the sequence editor, suppressing or handling this pop up would not be possible programmatically.
Alternately, follow the below mentioned approach:
- Write a script or a LabVIEW VI to copy the configuration files from the project directory to the TestStand Public folder.
- Run the script/VI. This step can be implemented via command line prompts to automate the process.
- Invoke an instance of TestStand. Once launched, TestStand will call the .ini file that you have recently copied from your project folder and will reflect the desired changes.
TestStand 2016 and later offer a setting called 'Environment' using which, you can load all the settings and files corresponding to the specific environment that you set. This will enable two TestStand system configurations to exist on a single system side-by-side. Further details about the same can be found here