On the Issue of Excessive Installation Time for LabVIEW Additional Components

[태민쓰]

The LabVIEW Runtime Engine installation is taking longer than expected. What steps can I take to minimize or optimize the installation time?

or

When deploying a LabVIEW application, the installer includes additional components such as the LabVIEW Runtime Engine and other dependencies. Is there a way to distribute only these components without deploying the application code itself?

[Yamaeda]

Yes, you can make an "empty" installer with only the Additional componenets. I usually make one of those as a "station setup" with whatever packages are needed. Then i can make small App installers and patches.

[thols]

Yamaeda's advice is good, but you will need to know/track what runtime-versions are required by your app releases. If you rarely upgrade LabVIEW and have all releases on the same LabVIEW-version, then there is not much to worry about, but if you have many applications spanning many LabVIEW-versions, and you sometimes update an application to a newer LabVIEW-version, then it gets vital to know exactly what you are doing. I wanted to do as Yamaeda advises, but I did not have the time to invest to make a watertight process, so I stuck with the old all-in-one installer.

And I would not trust the feature that allows newer runtime-versions to run older code, since that has broken installed applications on my customers PCs when another application with a newer runtime was installed. So I now always make sure the "Allow future versions of the LabVIEW Runtime to run this application" is disabled in the build settings.