LabVIEW Runtime Engine

[Nathan@home]

Hello!

I have a LabVIEW stand alone executable installed on a workstation. This old executable was installed using an "Installer" .  I did not build this executable. Today, I built a new stand alone executable and I wish to distribute this new executable using an installer. For this new executable, should I include within the "additional installers"  the default LabVIEW Runtime engine? I am concerned about two, potentially different, LabVIEW Runtime engines being simultaneously installed. A second concern I have is overwriting the existing Runtime Engine and breaking the old executable. What should I do? Any info on how LabVIEW handles differences in Runtime Engines? Thanks! -  John 

[RavensFan · Accepted solution]

LabVIEW can have multiple run-time engines installed.  So if you had a program that was built under LV 2017 and installed with the 2017 run-time, then later build another executable and installed with the 2018 run-time, those two run-times will coexist side by side.

Later, if you build another 2018 executable and an installer with 2018 run-time, when you go to install it, it will not install the 2018 run-time because it will recognize it already exists.

I often build an installer for new executables without including the additional installer and I'll use that for PC's that I know already have the run-time on it.  It just reduces the size of the installer.

[Nathan@home]

Thank you Ravens! - Johnathan (Nathan@home)