Making sure .vi files are open with the right version

[Retamoza_R]

Hello everyone.

Here's my situation: I need to have LabVIEW 2010 and LabVIEW 2011 installed in my computer, as well as VI's of each of these versions. Is there any way to have Windows open the .vi file with the corresponding version of LabVIEW? I know LabVIEW 2011 is able of opening VI's from both versions but what I want is to prevent the scenario in which someone opens this file and saves the .vi in the 2011 version by accident, thus preventing me from opening in other computers where only LabVIEW 2010 is installed.

Any suggestions?

[RavensFan]

You can't.

What you can do is vote for Version-aware LabVIEW launcher in the Idea Exchange.

[Yamaeda]

A good version control system (e.g. Subversion) and/or keeping files write protected is the current solution.

/Y 

[speksih]

We had a similar problem with our software and I just made main.bat -file for the main-VIs/projects in each project.

content in the bat-file fe.

"C:\Program File\National Instruments\Labview 2010\Labview.exe filename.vi"

OR

"C:\Program File\National Instruments\Labview 2011\Labview.exe filename.vi"

This way it opens allways in to the right LV-version.

This tho, doesnt prevent anyone from running your VI without the bat! 🙂

[Akiel]

im using virtual box from oracle to get round this problem, LV2010 on win7 then in the virtual machine LV8.6.1 on xp. And the great thing about this virtual box is that its free

[Retamoza_R]

"We had a similar problem with our software and I just made main.bat -file for the main-VIs/projects in each project.

content in the bat-file fe.

"C:\Program File\National Instruments\Labview 2010\Labview.exe filename.vi"

OR

"C:\Program File\National Instruments\Labview 2011\Labview.exe filename.vi"

This way it opens allways in to the right LV-version.

This tho, doesnt prevent anyone from running your VI without the bat! "

This seems like a good idea speksih, if one could only retrieve the file version with the same script and then probably hide the actual .vi file so it's not opened by accident....it could work.