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: 

Version information in EXE

Status: Declined

Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.

Builder should automatically attach version of LV to EXE so it can be seen in Windows Explorer. So you can always ask unexperienced end user about version. I drove 1000 km with wrong version of LV on my laptop... Upgrade to new version is not always straitforward... And I always forget to set version information manualy...
Active Participant

It's already there for the LabVIEW.exe:


 labview version.jpg


If you mean for EXEs you build with LabVIEW then I disagree completely with you.  The EXE should have the version you specified in the build spec.  And if you are doing things right, it should auto increment with each build.  There is no need to specify what version of LabVIEW was used to build the EXE.  If you are not including an installer for the RTE you EXE requires, then you can still download the RTE from


Certified LabVIEW Architect

I, ve ment this




Blank project, blank VI, everything default. I cant find LV version this exe was created.

For VI:


is clearly not working for exe.

Idea is that LV AUTOMATICALY by DEFAULT embeds version info into EXE file.

NI Employee (retired)

You can programmatically do this using .NET assemblies on Windows machines. Here is a community example ( that shows how you can find this. I agree with your idea though that the version information should be displayed by default somewhere. Either in the Title Bar next to the VI name when you run the executable of in the Help>>About page (this shows the LV version but not the Exe version). The .NET assembly works great for getting the information on a Windows machine but that won't work on Mac or Linux. If we displayed the version information or at least had a user option to display it then it would be OS independent and I wouldn't have to add this extra code to my executables.


You can also find this information manually by right-clicking on the exe file itself and choosing Properties and then the Details tab in Windows 7.

Proven Zealot
Status changed to: Declined

Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.

DNatt, NI

Check this cmd method....


tool version.JPG