ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

vb.net program determine if runtime engine is installed

Solved!
Go to solution

I have a vb.net application we are distributing and it calls a couple of vi's that I have bundled into a dll.  Obviously we need to have the runtime engine installed on the machines we are deploying this application to.  I was wondering if there was a registry entry or some other way to determine if the runtime engine was already installed on a windows machine.  

 

I know I could build my own installer and set registry keys, however the minimum runtime engine installer works and it is only 28 mb, where the smallest installer I have been able to build is about 140 mb.  So, as I said I am faced with two options, figure out a way to build my own minimum installer or figure out how to determine if the standard NI minimum installer is already install.

 

I haven't been able to find anything relating to this in my searches.

 

Thanks,

 

Eric.

0 Kudos
Message 1 of 4
(3,284 Views)
Solution
Accepted by topic author erfigge

There may be a more elegant way, but you could always check <Program Files>\National Instruments\Shared\LabVIEW Run-Time\####

 

EDIT:

 

Oh I found it by the way (with a little Regedit.exe searching):  HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW Run-Time\#### 

 

*where the pound signs represent the version number.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!
Message 2 of 4
(3,272 Views)

Indeed the registry is the way to go.  Here is a post on LAVA I did a while ago where I use AutoIt to get the different versions of LabVIEW installed (development or just RTE) and then run the appropriate version for the one installed.

 

http://lavag.org/topic/17803-run-exe-based-on-installed-run-time/

 

The source code is included so you should be able to understand the registry keys I read to find the versions installed.

0 Kudos
Message 3 of 4
(3,259 Views)

Thank you everyone.  Found the registry keys and that is exactly what I was looking for!

0 Kudos
Message 4 of 4
(3,255 Views)