Details about the property "Ver Num" in "Get Version" method.

[Ajay_MV]

Hi,

I'm trying to use the "Get Version" method to determine the source file (.vi/.ctl) version, whether it's 32-bit source file or 64-bit source file.  I got to see that this method outputs "Ver Num" numerical output but I couldn't find enough documentation about this number.  I'm wondering if this number would give some details about my search of 32/64 bit details.  I believe that this number must be associated to details like which version the file is created (LabVIEW 2016/2017...) plus other metadata like 32/64-bit version.

Does anyone has idea about this "Ver Num" property output from "Get Version" method?

Thanks,

Ajay.

[Ajay_MV]

@Darren 

Do you have any idea what the "Ver Nums" numeric output out there in this method?  I'm looking to differentiate between 32-bit vs 64-bit version of the LabVIEW file and wondering if this numeric output will help me.

The "Ver Nums" is consistent when I make changes in the source VI/Ctl.

Thanks,

Ajay.

[GerdW]

Hi Ajay,

set the display mode of the VersionNumber indicator to HEX!

Currently I'm using LV2011SP1 and get "11008008" for VI version.

With LV2017 I get "17008000" (no SP1 yet)…

[Darren]

The Version Number property returns the same value (385908736 with no patches installed) on LabVIEW 2017 32-bit and 64-bit. To my knowledge, there is no way to determine if a VI was saved with a 32-bit or 64-bit LabVIEW editor. If I later find otherwise I'll post to this thread.

[Mark_L]

We are using both 32-bit and 64-bit LabVIEW.  It would be helpful to have a way to determine if a VI was saved with a 32-bit or 64-bit LabVIEW editor.

[Kyle97330]

---

@Mark_L wrote:

We are using both 32-bit and 64-bit LabVIEW.  It would be helpful to have a way to determine if a VI was saved with a 32-bit or 64-bit LabVIEW editor.

---

I'm fairly certain that's not a thing you can do normally.

Can you say what problem you're actually trying to solve by doing this?  It sounds like you're presenting us with the Y part of the X-Y problem.

[Mark_L]

Knowing this will help reduce clutter and changes in our SCC.