LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

multiple labview versions on single machine

Is it ok to istall multiple labview version (eg. 5.2 & 8.5) on single machine?
well I fee it very difficult to use... but sometime its required?
 
What NI recommends?
0 Kudos
Message 1 of 14
(4,389 Views)
It is OK to use multiple versions.
No problems have been reported , as far as i know.
0 Kudos
Message 2 of 14
(4,386 Views)
"Pnt" <x@no.email> wrote in message
news:1203421205962-656590@exchange.ni.com...
> It is OK to use multiple versions.
> No problems have been reported , as far as i know.

Should be fine. One thing to be aware of though is that (XP at least) will
load the last used version of labview if you open a vi via Explorer.
Something to bear in mind should you be using the 8.5 version, close it and
then open a 5.2 vi in explorer. 8.5 will open it no problem but do a save
without realising and you'll not be able to open it again in 5.2!

Richard


0 Kudos
Message 3 of 14
(4,369 Views)
Hi Richard,

you can put the key "RegisterExtensions=False" in the LabView.ini to avoid this behaviour.

I run several versions of Labview (see signature) but only one version is allowed to register extensions (aka to run when opening a vi with explorer) - all other version get this key in the LabView.ini...Smiley Wink
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 4 of 14
(4,363 Views)
What I have done is going into Windows Folder Options->File Types and setup additonal right-click menu items for each version of LabVIEW installed.  So I can right-click on a VI and choose which version of LabVIEW to launch.  I can also set the default option from Open to Open in LabVIEW 8.5, so if I double-click on it, then it always opens in the LabVIEW version I typically use.
Message 5 of 14
(4,358 Views)

Does anyone know if a VI file has a known set of bytes that can be read to know what version of LabVIEW wrote it?  If we knew that, we could make an utility that gets called when opening a VI from a folder.  That utility would then read the byte(s) and then pass the VI on to the appropriate version of LV.  If only a newer LV version is installed, it could optionally be set to warn you that the VI was written with an older version.  Is there a technical reason why this hasn't been done already?

 

- Brad 

0 Kudos
Message 6 of 14
(4,100 Views)

Hi Brad,

 

"Is there a technical reason why this hasn't been done already?"

 

Well, no! And it is done already - you just have to search the forum for this tool (I don't have the time to do so at the moment...).

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 7 of 14
(4,079 Views)

It's called LabVIEW Version Chooser from DataAct.

 

Ton

 

EDIT: Hyperlink removed by moderator - DataAct website has been reported as an "attack site"

Message Edited by Support on 04-17-2009 08:34 AM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 8 of 14
(4,074 Views)
Firefox and Google Desktop do not like that site one bit.
0 Kudos
Message 9 of 14
(4,059 Views)

Hi,

we should remove this link, it contains spyware.

 

Mike

0 Kudos
Message 10 of 14
(4,054 Views)