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!
Top Kudoed Authors
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow installer to embed the LVRTE into the application directory

Right now, we can build an installer which embeds other installers (e.g. the LVRTE).  So we can distribute the installer and allow our customers to install everything they need using one installer.  This is great.  But I find that it sometimes disturbs my customers when they see that my application is also installing other things (i.e. LVRTE, DAQmx, etc).  They are curious about the "3rd Party Components".  I totally understand this.  When I download an installer, and see things like "Click here to also install Google Chrome" or Google Earth or some other spyware garbage, I am immediately suspicious.  Or worse, when I am not even warned about.  Bundling other installers is a common way to spread adware.  

 

Problem:

- Bundling third party componenets into an installer is suspicious to many users. 

- Bunlding extra installers also makes the un-intall process more complex (you have to uninstall things the extra stuff in a different step).

- Current method of bundling extra installers does not inform the user about all of the components being installed

 

 

So my suggestion:  Allow these components to be bundled (i.e. hidden) in the application directory.  I believe this is already possible with other run-time engines like the Java Runtime Engime.  And I see that something similar is possible with LabWindows/CVI (see here), though I have never used LabWindows.

 

I guess another way to do this is just to somehow hide the extra stuff from the user.  Do a silent install of all the 3rd party componenets.  But I feel like that is a bit devious, and might piss off some customers.

http://www.medicollector.com
2 Comments
Knight of NI

This looks like a duplicate of this idea.


LabVIEW Champion Do more with less code and in less time
Example Gatekeeper
Status changed to: Duplicate