App Method "Library.Get File LV Version" should work for files of newer LabVIEW Versions

[Jim_Kring]

I really think this is a bug, but I'm going to file this as a feature request, just to add more weight to the issue...

The VI Server Application method Library.Get File LV Version claims to be able to tell you the version of a Library (or XControl, XNode, LVClass) on disk, without loading it into memory.

Here are the docs:

But, when you try to call this method on a Library saved in a version of LabVIEW newer than the version of LabVIEW in which the method is executing, you get the following error:

Error 1125 (LabVIEW: File version is later than the current LabVIEW version.)

Why an error?  It had to read the version in order to generate the error.  Why not just return the version?

Thanks in advance for your kudos 🙂

[Darren]

The "Get File LabVIEW Version" method works as requested in LabVIEW 2012 and later

[Jim_Kring]

Woohoo! Thanks, Darren 🙂

[parthacg]

Bug is still existent (saw in LV 2018) for the method "Get VI:Editor Version Method".

Get VI:Editor Version Method

Short Name: Get VI Editor Version

Requires: Base Development System

Class: Application Methods

To Use: Create a method.

Returns the version of LabVIEW that last saved the VI. The version of LabVIEW that last saved the VI might be different from the file format version of the VI. For example, if you use LabVIEW 9.0.1 to save a VI, the VI has a file format version of 9.0.

To obtain the file format version of the VI, use the Get VI:Version method.

LabVIEW does not open the VI when retrieving the version information. If you specify a path to a file that is not a VI, LabVIEW returns error 6559.