Is it possible to start TestStand to automatically load with a custom environment

[ChrisFarmerWIS]

Hi,

I've created my own TestStand environment file:

But every time I open TestStand, it defaults to <Global> environment. And I have to open Configure --> Environment to change to my own environment, and press Set Engine Environment, which you then you have to wait for it to basically restart.  It's a time consuming effort every time you want to start TestStand!

Is it possible to change it so that it defaults to using my own custom environment?

Thanks in advance for any guidance!

[mateusz_owczarek · Accepted solution]

Hi Christopher,

I had similar problem and my solution (or rather a workaround) was to change shortcut target to:

"C:\Program Files (x86)\National Instruments\TestStand 2019\Bin\SeqEdit.exe" /env "MY PATH TO .tsenv file"

[ChrisFarmerWIS]

Thanks Mateusz.  Great tip!

[mateusz_owczarek]

You're welcome, glad I could help 🙂 

[DavidWilt]

---

I had similar problem and my solution (or rather a workaround) was to change shortcut target to:

"C:\Program Files (x86)\National Instruments\TestStand 2019\Bin\SeqEdit.exe" /env "MY PATH TO .tsenv file"

---

This is not a workaround this is actually how NI expects you to do it.  I opened a support ticket with them in the past and this was exactly how they instructed me to do it.

[HasbunWoodEng.]

Hi everyone,

for anyone working with environments and/or multiple Teststand versions: I put together a small open-source tool called Environment Toolkit for TestStand that helps manage and launch TestStand setups using simple profiles (version + environment), via CLI or GUI.

You can install it through vipm.io 

or github.com 

Best,

Juan

[python007]

---

@DavidWilt wrote:

---

I had similar problem and my solution (or rather a workaround) was to change shortcut target to:

"C:\Program Files (x86)\National Instruments\TestStand 2019\Bin\SeqEdit.exe" /env "MY PATH TO .tsenv file"

---

This is not a workaround this is actually how NI expects you to do it.  I opened a support ticket with them in the past and this was exactly how they instructed me to do it.

---

If it this is like NI exepts to do it whats about the CfgLocation (e.g. Users.ini)?

My workaround is that i have for every environment I use I created a registryfile to switch between the environemnts:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\National Instruments\TestStand\23.0]
"CfgLocation"="D:\\teststand_environment\\CommonAppData\\Cfg"
"DefaultEnvironmentPath"="D:\\teststand_environment\\tw_teststand_environment.tsenv"