How do I see what version my LABVIEW code was written in?

Updated May 5, 2020

Reported In

Software

  • LabVIEW 2009 Full
  • LabVIEW 2016 Full
  • LabVIEW 2017 Full

Issue Details

I am using old LabVIEW code and I'm running into compatibility issues with my current version of LabVIEW. How can I see what version I should use that will be compatible with the code that I have?

Solution

There are several ways to determine in which version of LabVIEW a VI was saved:

 

  • Method 1: The easiest way is under File»VI Properties. The Source Version (the version the VI was originally written in) appears under the General Category in the drop-down menu, as seen below.

 

  • Method 2: To get the source version programmatically, use the Application Invoke Node (LabVIEW 7.0 and later): Get VI Version. See the example block diagram below.

  • Method 3:  As of LabVIEW 8.6, if you attempt to open a VI that was saved in a newer version of LabVIEW, an error message will pop up displaying the version of LabVIEW the VI was saved in.

 

Additional Information

In the VI Properties, you can also enter or review notes on your particular version under Revision History.

Prior to LabVIEW 7.0, you can programmatically examine portions of the VI code to determine its version. The attached example SortByVIVersion(OLD).llb contains a demonstration of this technique.  This technique is no longer supported and will result in errors in new versions of LabVIEW.

If other methods are unsuccessful, open the VI in the earliest version on your computer.  If an error occurs, the VI is saved in a later version.  Close the VI and repeat this process for the next version of LabVIEW.  The first version that opens a VI without any error is the version in which the VI is compiled.

Attachments

SortByVIVersion(OLD).llb

Related Links

How to Upgrade or Revert a VI to a Different Version of LabVIEW

 

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.