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: 

Installer and ZIP File Build Specification should have the possibility to use Pre-Build VI and Post-Build VI

Status: New

All the other Build Specification has already this function available. Why not the Installer and the ZIP File.



LabVIEW ChampionArchitect
Active Participant

Would love this to allow me to zip installers and copy to a distributable directory.

James Mc
CLA and cRIO Fanatic
My writings on LabVIEW Development are at
Proven Zealot

And also please make it an array of pre and post build action.


With an executable, it's pretty annoying that you have to make a VI to combine several actions, only because you can select just one VI.



I have one code base (lvproj), that has 2 specific flavors A and 2 specific flavors of B, so I get 4 executables. I set 2 project  with pre build actions (as it still (at least in 2013) cannot be set in the build script, *sigh*), but I need 4 VIs for setting A1, A2, B1, B2, and then 4 other VIs just so the build script can set A1 B1, A1 B2, A2 B1, A2 B2. At some point I'll get 3 flavors of A and\or B, or 3 specifics (A, B, C). This doesn't scale up well at the moment...

I'd say an array would almost be easier to implement as well, but that should be irrelevant. Now there is 0..1, With an array you'll get 0..n.