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!
cancel
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
17 Comments
Member

I still can't believe NI hasn't added this yet.

Trusted Enthusiast

YES! I havebeen wanting this fir years!

-------------------------------------------------------------------
Unfortunately, most readers of this Forum, including some real Experts, have not mastered the skill of being able to read the code that Posters fail to post. If we cannot see "what you did wrong", we are unable to tell you how to fix it. (Bob Schor 28 August 2018)
Member
This would indeed be extremely helpful. I'm quite surprised it doesn't exist already.
Member

kudo from me. Smiley Mad

Member
Status changed to: 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.

Active Participant

Can't understand why this has been declined, it should be relatively straightforward and would be incredibly helpful....

 

 

Member

I agree. As much as a subscription for this software costs, things like this should be made easier to accomplish as it provides more justification for the expense.