Is there an equivalent property (Hist.Revision) for executable?

[Ray.R]

I wanted to display the revision of the code within the executable by getting the current revision from the main VI's property Hist.Revision.

This works great in the development code but gives an error 1043 in the executable version.

Is there an executable equivalent to this?

Thanks,

RayR

[LandBelenky]

I'm tagging this because I'm also interested in the answer.

[Matthew_Kelton]

Can you not just use the EXE version instead of the VI rev number?

[Matthew_Kelton]

If you can use your EXE version, see here.

[smercurio_fc]

My memory is a little fuzzy on this, but if I recall correctly, I think the revision information is removed once you build the application, so I think the only option you have is to use one of the methods that have been posted on extracting the exe version number.  A recent one: http://forums.ni.com/t5/LabVIEW/Can-I-find-the-version-of-my-executable-built-with-the/m-p/1121206/h...

[JÞB]

Here is a toy I keep on hand.  I use it in just about every solution I deliver for creating banner information, About.vi's, conditional code switching, etc....

Its been useful- enjoy!

[LandBelenky]

As an aside, Jeff: why do you use the While loop with hard-wired stop condition?

[smercurio_fc]

---

@LandBelenky wrote:

As an aside, Jeff: why do you use the While loop with hard-wired stop condition?

---

That's known as a Functional Global. Or a LabVIEW-2 style global. Or an Action Engine.

[JÞB]

Short answer- it give me a Uninitialized Shift Register that acts like a data storage unit.  see the First call primitive? I never exicute the .NET calls again while the SR is within lifetime. and subsequent calls to the Action Engine get the data on the SR rather quickly.

Long answer: Here is a link to what you see after going to my profile page and clicking the Required_Reading tag.  Start at the bottom of the list

EDIT: Saverio's link is the oldest tagged Required Reading thread

[rolfk]

---

@smercurio_fc wrote:

My memory is a little fuzzy on this, but if I recall correctly, I think the revision information is removed once you build the application, so I think the only option you have is to use one of the methods that have been posted on extracting the exe version number.  A recent one: http://forums.ni.com/t5/LabVIEW/Can-I-find-the-version-of-my-executable-built-with-the/m-p/1121206/h...

---

Yes History information along with version number etc is removed when the VI is build for inclusion in a build app. I think it used to stay in the VI (~Version 7) when you did configure a VI to not have it's panel removed, but this is undocumented and not guranteed, and I would never rely on that. Also it may have changed since and get removed anyhow in modern LabVIEW versions, or going to be removed in the future.

Pesonally I use Tags (another undocumented feature ) if it's VI specific and the executable version number if it's application specific.