Determining Current Version of LabVIEW runtime

[TrackerMan]

I am trying to determine where LabVIEW is installed to install my application files. I am using HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabView\7.0 registry key to find the LabVIEW install path. I plan on adding a look at the Current Version key to determine the current version. I wanted to the the same for the LabVIEW Runtime when LabVIEW is not installed. It appears the the LabVIEW Runtime does not have a Current Version registry entry. Is there a way to determine the current LabVIEW Runtime version?

Thanks,
Alan Howard
Huntron, Inc.

[Randall_T]

Here is a quick example that might help.

Good luck
Randall

[TrackerMan]

Thanks Randall,

This looks like it would work great for a LavVIEW Program. Unfortunately, I have to do this from my install program which is not a LabVIEW application.

[Randall_T]

Sorry I misunderstood the question before.

This may not help either but� \Program Files\National Instruments\Shared\LabVIEW Run-Time\ (runtime version) is typically where I find the runtime directories for the various run time versions I have installed support for.

[DD]

The Application property App.Version seems to show the LabVIEW version even
with built applications.

"TrackerMan" wrote in message
news:50650000000800000075D30000-1079395200000@exchange.ni.com...
> I am trying to determine where LabVIEW is installed to install my
> application files. I am using HKEY_LOCAL_MACHINE\SOFTWARE\National
> Instruments\LabView\7.0 registry key to find the LabVIEW install path.
> I plan on adding a look at the Current Version key to determine the
> current version. I wanted to the the same for the LabVIEW Runtime when
> LabVIEW is not installed. It appears the the LabVIEW Runtime does not
> have a Current Version registry entry. Is there a way to determine the
> current LabVIEW Runtime version?
>
> Thanks,
> Alan Howard
> Huntron, In
c.

[altenbach]

I would highly recommend NOT to put your application files in the same place where labview (or the runtime) is installed. These need to e kept separate or you'll run into problems next time you upgrade labview. I would recommend a static, unique path, e.g. "c:/program files/myapp/..."
Also, be aware that multiple versions of LabVIEW can exist on a single machine, and the "current version" is whatever has been used last.

Even more so with the runtime engines. All versions can coexist and most PCs here at my location have versions 5.1, 6, 6.1, and 7 installed in order to run older as well as more recently built applications.

Since built applications have the diagram removed, you cannot run older builds with newer engines and the correct version need
s to be available, corresponding to whatever you used to built the application.

For this reason, there cannot be a "current version" for runtime engines. LabVIEW picks the single correct version, which MUST be available.

[RGSchmidt]

He slightly mistated what he needs. There is the application which is in a user defined directory and then he needs to install the device drivers in the instr.lib directory that resides in LabVIEW 7.0 or 7.1 etc. and he is trying to find an easy way to determine where to install the drivers. If LabVIEW is installed then everything works nicely.

Later.

Randy