VIs that Contain TestStand References cause Dirty Dot Half the Time

[TheQ]

So we've see this problem on half of the machines where just opening a VI that contains TestStand references cause the VI to be dirty.  My first thought to investigate this is to check if compiled code is separated.  It currently is not and I'll be taking that up with the customer.  However, that fact this only happens on half of the machines leads me to believe that is not the underlying cause.

Has anyone else seen this? Are there thoughts on what else I can try?

[RaviShrigiri]

Hi,

Please check :

1) What was the VI and TestStand version earlier and now?

2) The VI maybe referencing some TestStand VIs which was from an older path ( read older TestStand version) and now its being opened in a PC which has newer version of TestStand.

If you can post a simple VI which shows this behaviour then probably others can try and give some inputs.

Ravi