Improve TestStand version selector

[Ray.R]

There are many reasons why TestStand is not my language of choice....  I will start with this one...  The TestStand Version Selector needs improvements.

If the users are to base the reliability on the interface, then the TVS needs to be much more reliable.  When switching from one version to another, the version selector hangs more often than being able to accompish its task.  The TVS just sits there pretending to do something...  well... it probably was doing something, decided it was lost and then decided to sit and watch the CPU clock cycles go by...

I usually kill the task and try again... By the 3rd attempt, it will somehow manage to switch versions.  These attempts give me enough time to write this idea.. After killing the application, I always get the "Unable to determine the current TestStand version" message.  This is usually a good sign as the next attempt will probably be a lucky one.

I decided to search the forum to see if others had issues with TVS, and of course, I was not alone.  Se the links below:

http://forums.ni.com/t5/NI-TestStand/Operation-failed-popup-when-using-TestStand-Version-Selector/m-...

Josh W is not a novice at TestStand...

http://forums.ni.com/t5/NI-TestStand/Problem-launching-TestStand-2012/m-p/2401666/highlight/true#M40...

http://forums.ni.com/t5/NI-TestStand/Microsoft-Visual-C-run-time-error/m-p/860288/highlight/true#M23...

Just how long is being patient?  I have waited more than an hour (during lunch) and it still does not swap versions...

I do realize that most issues are related to microsoft visual studio or visual C++, but TSV needs to tell us what is going on or why it is not able to switch version.  After all, once it finally changes versions, TestStand is fine.  No changes to the PC or any software installation.  So the issue clearly points to TVS.

When you improve the TestStand Version Selector, can you also improve the time it takes to change versions?  I realize it's too late to improve the architecture of the language where different version could co-habitate together, like LabVIEW, but at least make it a bit faster.. 

Now that it has selected the approrpiate version, I shall stop my rant... I mean idea and get back to work.

Hopefully all the people who share the same concern will kudo this idea.. 

🙂

[dug9000]

http://forums.ni.com/t5/NI-TestStand/Operation-failed-popup-when-using-TestStand-Version-Selector/m-...

This was presumably due to Windows security settings being set to a high security mode which locks down things the version switcher is trying to do. Most users should not encounter this problem.

http://forums.ni.com/t5/NI-TestStand/Problem-launching-TestStand-2012/m-p/2401666/highlight/true#M40...

This seems like it was likely a problem with a 3rd party product that the version switcher tries to integrate TestStand with. The user who encountered this issue never got back to us on whether or not the recommended remedy of trying the workarounds recommended by the 3rd party worked.

http://forums.ni.com/t5/NI-TestStand/Microsoft-Visual-C-run-time-error/m-p/860288/highlight/true#M23...

This issue had two users reporting it with two different problems, one user's problem was with their own dlls, recompiling them with a newer version of visual studio fixed their problem. The other user had to repair their installation of an old labview runtime engine.

I think part of the problem is that version switcher is trying to integrate with 3rd party environments over which we have little or no control. I think it's valid that the version switcher could better inform the user what it's doing so that they have a better chance of figuring out why it's failing and perhaps give the user more control over which environments it tries to integrate TestStand into and when.

The version switcher should only take a few minutes. If it's taking longer than that it's probably hung. If you'd like help in determining the cause of an issue with it please let us know.

-Doug

[Ray.R]

Sure...  anything to help improve this application.

I fully understand the issues / limitations due to the integration with 3rd party environments.  If the (initial) improvement is to provide feedback to the user or at least not get hung (watchdog timer / timeout on activity), then that would be a great improvement.  I've seen this behavior on multiple machines, including a couple of NI-PXI systems. 

The point I was trying to make is that irregardless of the source of the problem (Visual Studio, old LabVIEW RT engine, DLLs, 3rd party product, security settings, etc) these should not cause the Version Selector to hang or simply give up.  As you mentionned, providing feedback to the user so that the issue can be remedied is important.    That is why I posted this as an Idea rather than a bug.  Had I reported it as a bug, the finger would have been pointing elsewhere.. 😉

[都会好的]

Hello Ray.R I do not know if you had improved  this issue. Now, I also meet this error. I had attempt to re-installing or another ways but still  never to solve.Whether anybaby have good purpose,Pls feel free to share, Thank you at advance.