Is there a way to read the RTE version of an executable without opening it?

[AMP12]

All,

I'd like to find a method of determining which runtime engine is needed to run an executable programatically.  I'm working on an auto-updater program and have read dozens of forum posting on the topic.  I've found the Application property node for version number in the DevEnvr, and the FileVersionInfo.VI to read the build version number, etc. in the RTE.  The coding for updates within the same RTE is done and works fine.

The one thing that is absent from all of the postings is a technique to determine the RTE needed to open and run an executable.  Is one out there?

I've already got the code working to install the new version of RTE, but I'm at the last (skipped earlier) step of determining when that is needed.  Right now I've resorted to writing it in the build properties version information description and parsing it out.  I fear this flimsy work around could be easily missed on the next upgrade if someone doesn't read the documentation and include it.

I just found this Idea Exchange  which looks like a suitable solution is going into NI R&D as of a couple days ago.  But until that is released, is there a more robust way of determining this?

[crossrulz · Accepted solution]

Here's a recent thread about this:http://forums.ni.com/t5/LabVIEW/LabVIEW-Version-of-Built-Executables/td-p/2162718

In short, we found a way to read the EXE as a text file and performed a search for a specific pattern.

[AMP12]

Works great!   Tested in EXEs from 8.5 through 2011 and all is good.