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: 

Single File Installer from LabVIEW

Status: Declined

 National Instruments will not be implementing this idea. NI has no plans at this time to change the file structure of the 'Installer' build spec output. The current workaround is to zip up the installer build output yourself, or use a 3rd party program to create a single-file installer.

Currently in LabVIEW if you build an installer you end up with a hierarchy of files that look like this:

 

singlefile1.png

 

If you want to distribute this installer via the web, you need to use a third party program to zip it up, or create a self-extracting zip file.  Since LabVIEW can already create zip files with no problem, I propose the ability for LabVIEW to create a single file installer that can easily be distributed, like this:

 

singlefile2.png

 

This can be as easy as a checkbox in the current installer Advanced page:

 

singlefile3.png

12 Comments
Knight of NI Knight of NI
Knight of NI

I would say that this should probably be the default. Most people don't care about all those files.

 

That said, this doesn't bother me that much personally, as I don't create that many installers, and when I do, we usually run them ourselves.


___________________
Try to take over the world!
Trusted Enthusiast

If not this then at least provide an option to automatically create a self extracting ZIP file file. Distribution is much easier when you have a single file.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Knight of NI

I would agree with this idea. I've stopped creating installers using the Application Builder. I use Inno Setup. WAY more flexible.

Knight of NI

It would also be nice to be able to customize the icon of the single file installer.


LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
Knight of NI

This would also be extremely useful for source control.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Active Participant

And make a similar one for Real-Time targets. With no need for NI Max, and with the option to include the OS as well....that way we could just click on the installer, get a list of available targets (and or input an IP) -> select one or multiple targets, and install it in one go! Setting up multiple PACs today is way too cumbersome and requires too much software. Pack it all in one stand-alone installer.

 

(Yes, this should be posted on the RT Idea Exchange...but I  mention it here because it's really about the overall philosophy for distribution that should govern all parts of NI's products; keep it as intuitive and smart as possible.)

MTO
Check out ClampOn CAN Monitor on the LabVIEW Tools Network.
Member

If I have a LabVIEW exe with about 2MBs and my installer is about 150MB I can't send such an installer via e-mail. In such cases I miss the old slim LabVIEW installer that only handles the files he should do. This is much besser for client updates as building a complete net big installersourus.

---------------------------------------------------------------------------------------------------------------------
Dipl.-Ing. (FH) / CLA / MCTS
Knight of NI

> If I have a LabVIEW exe with about 2MBs and my installer is about 150MB I can't send such an installer via e-mail. In such cases I miss the old slim LabVIEW installer that only handles the files he should do. This is much besser for client updates as building a complete net big installersourus

 

Well, this is a different issue. The number of installer files is not correlated to the installer size. If the run-time engine is included in the single file installer proposed here, it will not be small! You migh want to look at this idea instead.


LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
Member

That's awesome.

Member

A single installer file would be great.

 

I had to fix a couple co-workers SVN folders because of this. They pushed in the installer to SVN. Then added features which in turn created more files\folders in the installer directory. This really made SVN angry. files were now missing new folder were created. SVN didn't know what to do. Had to remove the installer from SVN and then add it back.

 

I only use SVN for source code and put my installers into ZIP's, then to a web server in the company. I need to sit down with evryone and get a software release procedure going.....

 

...anyways, great idea. I hope NI looks at this and implements it soon.

 

Also, I wish we had the option to specify the folder! not always volume!

 

 

- A minute saved is a Minute earned!