LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Support for Additional 3rd Party Installers when building an Installer

Status: Declined

The referenced document describing how to use Post install actions is the best way to do this.  All of the effort going forward will be based on packages using the NI Package Manager.  NI will not be adding additional functionality to Windows Installer options.

When creating an installer for a built LabVIEW application, it is very difficult (see here) to include an additional 3rd party installer (such as a device driver or application that your built application depends upon).  What I'd like to see is a solution that treats 3rd party installers as first class citizens.  I'm imagining a new "Additional 3rd Party Installers" page of the Installer build specification properties dialog.


2-3-2010 1-35-27 PM.png


This page might look something like the one in the screenshot below, allowing users to add a folder that contains the 3rd party installer files and define a command that is run inside that folder during the install process.


2-3-2010 1-41-08 PM.png


When LabVIEW builds the installer, it would suck the additional installer folders into the main installer and, after installing your app files and the additional NI installers, it would sequencially extract your additional 3rd party installers into a temp folder and then execute the command line to run.  This is a pretty simple scheme that would really simplify the process for end users.


I'm sure I didn't address every issue of this use case, so please, everyone, feel free to add your own ideas.  I'd love to hear your comments.

JKI Blog
Active Participant
I usually build an extra installer with all my extra stuff in it, and it's a pain!  I'd love to see everything in one place...

Copyright © 2004-2020 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.
Installers for LabVIEW applications are such a pain - this would certainly be a very welcome improvement (and along similar lines, maybe the option to detect & install .net so that our users dont end up with the rather confusing "the VI needs the full development in environment error")
Proven Zealot
A very useful ask. Kudos.
Active Participant
Active Participant

A really useful idea. Kudos.

I think that also these additional installers should be executed with the same User rights as the LabVIEW application "setup.exe".

Let me explain:

if I right click over setup.exe and select (Run as... - Win XP) or (Run as Administrator - Vista and 7), also the additional installers should be launched with the same credentials (without re-typing the password), or their installation could fail..

In claris non fit interpretatio

Using LV from 7
Using LW/CVI from 6.0

Please consider the addditional suggestion to this idea here




Message Edited by SanRac on 02-16-2010 03:27 AM
NI Employee

I love this idea. 


I would like to point out one thing, however, which could open up a bag of worms.


There is another idea about auto-detecting which installers are needed when building an executable.  Incorporating this idea with yours seems like the next logical step, but it would be terrible to expect any NI software to automatically detect needed third-party installers.


Like I said, your idea alone is GREAT.  I'm just thinking that if these two ideas were developed together, it could be very troublesome.

National Instruments
Active Participant

Yep, very necessary, 5 star idea!!!


KUDOS.  This is so useful it should be a patch, and not something in a new version




UofL Bioengineering M.S.

"I had rather be right than be president" -Henry Clay

************* Its pain!!! I look forward to!

Yasemin Barutçu
Electrical And Electronics Engineer
Active Participant

Have a look.......

Thanks and Regards
Himanshu Goyal | LabVIEW Engineer- Power System Automation
Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
It Only gets BETTER!!!
NI Employee

Is there any feedback about this idea from the R&D team? It could make our lifes ten times easer If LabVIEW has this function.