Installing LabVIEW runtime engine files with third-party MSI builder. Is nipkg, the new way?

[Michael Aivaliotis]

I use a third-party MSI builder and not the built-in NI installer builder. I want to include the latest MSI LabVIEW runtime installer. I looked through: C:\ProgramData\National Instruments\MDF\ProductCache but couldn't definitely determine the correct files to use. I used the NI installer builder as a guide to determine the dependancies.

I know the LabVIEW runtime is also available as an nipkg file. is that the better way to go? If someone can suggest any other solution that would help, I appreciate it.

[Neil Pate]

I use InnoSetup for a custom installer and I also install the 2019 runtime this way.  It may not be the "right" way to do it, but the way I solve this problem is to manually extract the runtime installer and then just include that directory in my installer and run the Install.exe from the installer.

 

 

Edited June 21, 2021 by Neil Pate

[hooovahh]

So one thing I have done in the past is generate an installer using Application Builder, but not include any VIs or EXEs.  Then you can call this NI installer silently from something else like InnoSetup. 

[LogMAN]

I too use InnoSetup to extract and install various products. Regarding the installer, I'm not sure if you are aware of this, but you can get offline installers from the downloads page.

My installer also does a silent installation of NIPM and various packages. The details are explained in these KB articles:

• Automating the Unattended Installation of NI Package Manager (NIPM) - National Instruments
• How Can I Control NI Package Manager Through the Command Line? - National Instruments

If I remember correctly, the parameters described in the first article should also work for other offline installers.

Nevermind, here is the description for individual offline installers: Automating an Installer - NI Package Manager 20.7 Manual - National Instruments

Edited June 21, 2021 by LogMAN