I am getting very frustrated with VIs not running when called from TestStand, returning errors that claim the VI is broken, then when I go look at the VI it runs just fine.
Whenever I move the project or deploy to one of our test machines, I always have to do a mass compile. On my latest move, I did Mass Compile and it still does not run.
I tried the 3 troubleshooting steps in the error message to no avail.
It's almost like the runtime can't find these file while the dev environment can, but that seems silly.
What am I doing wrong? Is there some fundamental change I need to make in my development practice to eliminate this behavior?
I don't know how to even start solving this because the messages seem to make false claims. It claims a file is missing and then I find it exactly where it said it should be. Says a VI is bad, yet runs just fine.