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: 

Slim app builder

Status: New

One thing prevent our company to upgrade to newer labview is that the run-time engine gets too big. Even I really like the features in later version, I still have to save the files back to 7.1 then to 7.0 to build application installer. Under 7.0, the run-time engine is very small, and the installer is less than 10MB and I can easily email the program to customers. In version 8.0, the run-time engine is 65MB and now the latest version is well above 100MB.


What I would like to see is that application builder get smart, only pick what is needed and build slim app.

Trusted Enthusiast

I think this is actually the first idea that explicitly asks for this, but exactly what you asked for is discussed here in Build executables that don't require a runtime engine and Segment the LabVIEW Run Time Engine (RTE) to ONLY Necessary Components.


Let me get this straight... you're using the current development environment (8.6.1, or 2009), but you're using Save for Previous Version all the way down to 7.0 just for the smaller installer?


Anyway, I agree wholeheartedly. Kudos.

Wirebird Labs: Expert Toolkits for LabVIEWDeploy, by Wirebird Labs: Expert Toolkits for LabVIEW
Proven Zealot
I agree and kudos!!!

Our email system only allow attachment less than 10MB, and I think most of the companies also have size limit for their email system.


I am actually only use version 8.0 but I am playing with evaluation copy of 2009. I am not sure if these new features will work when I save them back to version 8.0 then to version 7.1 then to version 7.0. That is kind hassle already to have three version of labview installed on my computer plus managing all these files for different version.


Don't let LabVIEW becoming windows and grow bigger for each release.  Thanks for support.

Knight of NI

Nobody in his right mind should distribute applications via e-mail. Host it on an ftp server or web page and e-mail out links to it.


This way you can also update the application at any time, preventing people from installing a stale application from an ancient e-mail message. 

LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
For serial users, e-mail is not good choice. But for what we have to send to customers, and for a couple MBytes size small program, it is definitely overkill to ask customers to download and install a 100 MB package.


I upgraded my LabVIEW from 7 to 2009 and the installer shot up from 15Mb to 1.2Gb. I nearly fell off my seat! For this reason, some of my other project teams have declined to upgrade to 2009 and now I need to support multiple environments.


Surely the included installers could intelligently leave out al teh sub components which aren't used by the project?


Here's an imaginary (but not too far fetched) scenario: one of the reasons some of my customers like LabVIEW over line-based languages is that they're not necessariy very good with the whole computing thing, so they like little pictures. If I suggested the jack in to my FTP server, they'd probably think that was some new swear word.



This would be a huge benefit to me also.  Sometimes I do a remote install using a VNC connection, often when a PC is being replaced at a lumber mill site.  The applications typically are not super complex and run either DAQ or serial or TCP/IP controlled instruments.  I keep a copy of LV 7.1 for just these kinds of applications, since it is stable on Windows XP, and can be installed quickly.