Getting the .llb file version programatically when using an executable

[77maxmustermann]

So Im having a problem

I found this clever VI that gets you the Version of a .llb file that is situated inside of a Project.

The problem is when I convert my VI to executable it wont work anymore any idea how to make this vi compatible with both vi and exe?

Thanks

[Hooovahh]

This code does not get the version of an LLB, and LLB doesn't have a version.  It does have VIs in it that are saved in a version of LabVIEW but this version doesn't change unless it has been mass compiled.  What you have is code that can tell you the versions of the libraries in a project.  In an EXE there is no project, so there is no way this would work.  You can still get the version of the library and this can be done by using the Invoke Node on the Application Instance for Library >> Open.  Then using a property node you can read the version.  But for this you'll need the path to the library.  There are multiple ways to get this and without knowing more on your side I don't know which method would work best.

[altenbach]

I agree with the above, but I am also curious about the purpose of this entire exercise? What are you actually trying to achieve with all this?

[Andrey_Dmitriev]

---

@altenbach wrote:

I agree with the above, but I am also curious about the purpose of this entire exercise? What are you actually trying to achieve with all this?

---

Christian, most useful use case for this is PlugIn architecture, when the code distributed as libraries and each library should have own version (like DLL version).

I stil using old-school LLBs for distribution. Each lvlib "compiled" into LLB and the lvlib also placed into LLB, then the version can be obtained from binary LLB by searching <Property Name="NI.Lib.Version" Type="Str">x.x.x.x</Property>. Dirty trick which works. More elegant solution would be to distibute PlugIns as packed libraries - then the version can be obtained programmatically.