Find installed Versions of LV From the Dev Env

[paul_a_cardinale]

From the development environment, I want to find the locations of all installed versions of LabVIEW.

Initially, I used this:

Then looked down from there.  But (in Windows) that may return either "C:\Program Files (x86)" or "C:\Program Files".

What can I do to find all installed versions, on any platform?

[Bob_Schor]

Hi, Paul.

     The problem might be that if you use LabVIEW's "Application Files" with Get System Directory, it will (probably -- I haven't tested this as I "cleaned off" my system that had both 32-bit and 64-bit LabVIEW installations) return either "<Disk Drive>:\Program Files" for 64-bit LabVIEW or "<Disk Drive>:\Program Files (x86) " for 32-bit LabVIEW, so you probably should run it twice (once using what "Get System Directory" returned, and once for the "other-bittedness" version.

     Now its just a matter of searching in "Application Files" for files of the form "LabVIEW.ini" and seeing what folder (such as \LabVIEW 2024) they are in.

Bob Schor

[raphschru]

Hi,

Here is my VI to get all installed LabVIEW versions (32/64-bit) on Windows.

It is derived from a VI from Hooovahh.

It is using Windows registry, so it will only work on Windows.

I don't know how it is stored on Linux or MacOS.

Regards,

Raphaël.

[paul_a_cardinale]

---

@Bob_Schor wrote:

Hi, Paul.

     The problem might be that if you use LabVIEW's "Application Files" with Get System Directory, it will (probably -- I haven't tested this as I "cleaned off" my system that had both 32-bit and 64-bit LabVIEW installations) return either "<Disk Drive>:\Program Files" for 64-bit LabVIEW or "<Disk Drive>:\Program Files (x86) " for 32-bit LabVIEW, so you probably should run it twice (once using what "Get System Directory" returned, and once for the "other-bittedness" version.

     Now its just a matter of searching in "Application Files" for files of the form "LabVIEW.ini" and seeing what folder (such as \LabVIEW 2024) they are in.

Bob Schor

---

Hi Bob,

Yes, that's what's happening.  But what I am looking for is a single execution of a VI to find all instances of LV installations.

[Bob_Schor]

Raphael (two posts earlier) provided Just What You Wanted.  Very nicely done (I gave it a Kudo).

Bob Schor

[paul_a_cardinale]

---

@Bob_Schor wrote:

Raphael (two posts earlier) provided Just What You Wanted.  Very nicely done (I gave it a Kudo).

Bob Schor

---

Not quite.  I want something that works on any platform; not just Windows.

[Bob_Schor]

---

@paul_a_cardinale wrote:

---

Not quite.  I want something that works on any platform; not just Windows.

---

Aha!  I suppose that, in principle, the method I suggested could work in a Linux environment (I recall writing a utility that "knew" (or "figured out", don't remember which) where the myRIO Toolkit saved LabVIEW RealTime routines, or you could write code to "go looking" and figure it out, but it's like middle eastern bread, a (potential) PITA.  Even less (= zero) experience with LabVIEW on a Mac.

Bob Schor

[rolfk]

LabVIEW on a Mac is only in so far easier than Linux that you have one manufacturer instead of a myriad of distributions. Other than that Apple likes to move around recommended locations just as much or more than anyone else. And then introduce APIs to query them and deprecate those APIs within a few years for security concerns or simply some whim of a developer.

[Yamaeda]

What if they've installed it in a non-standard directory? The environment variable ProgramFiles and ProgramFiles(x86) gives the standard installation paths and it might be good enough to search for labview.exe from there, but not 100%.

[paul_a_cardinale · Accepted solution]

Since I really only needed paths to the preference files, I extracted pieces from raphschru's code and merged it with code for the Mac.