HowTo bring LV Application Builder to create VERSIONINFO section in *.exe?

[red-ant]

Our goal:
We want our LV application (*.exe that runs on LV RuntimeEngine) to have the standard Windows VERSIONINFO section as part of the *.exe.

Why?
- Because we want to use Windows Explorer to show the file- and product version of our LV application (properties of file).
- Because other (non-LV) applications should be able to read the LV-application's version [via Windows SDK GetFileVersion()] to check for compatibility.

What is Windows VERSIONINFO section?
-> see attachment
-> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/tools/versioninfo_resource.asp

This two posts do NOT answer the question 😞

How do I display the VI Version number on the front panel?
http://forums.ni.com/ni/board/message?board.id=170&message.id=58271

Why doesn't the exe file made by Build reflect the version number of the vi used to make it???
http://forums.ni.com/ni/board/message?board.id=170&message.id=95440

[tst]

Nice question.
I'm not sure this is possible. If I understand the msdn documentation
("To include resources in your Windows-based application with RC (Resource copmiler), do the following:
4. Link the compiled resource (.RES) file into the application's executable file with your linker.")
correctly, this is a property of the compiler (you have to link the file into linker).
There doesn't seem to be an option for this in the application builder.
You could try making a product suggestion.

[chrisger]

Hi there

if you have MS Developer Studio you can open your LV-App.exe (see Attachment DVS_Open, make sure to open as "Ressources"). After that you can add ressources to your App (see attachment Add_Version) by right-clicking on your app in the tree, e.g. "Version". These Version info than will be shown like in the jpg you posted. You can create a ressource script (.rc) in DevStudio to automate this process, but see msdn.com for more info.

best regards and let us know
chris

[Joe_Guo]

It would be nice for NI to separate the application builder into 2 steps, first build the exe, next, use the built exe to create installer files (with or without the runtime engines). Between step 1 and 2 you can modify your files, add/remove files, etc.

-Joe

[red-ant]

Hi Chris,

thanks for your idea! We had a similar one and tried it befor we posted the thread. Now we tried again in the exact way you proposed.
The problem is that if we do so DevStudio adds the new ressource but removes the complete (!) code section out of the *.exe file. So the LV-application does not run any more. The problem can already be seen by the new filesize of the application.

If you do not see this phenomena, please let us know!

Thanx and best regards,

Oliver Thost.
red-ant measurement technologies and services

[red-ant]

Hi tst,

we just did a product suggestion, thanx for that idea.
But still we are searching for a (quicker) solution...

One part of the NI product suggestion form is the question:
"4. Is there a workaround?" Right now there is no working workaround.

Best regards,
Oliver Thost.
red-ant measurement technologies and services

[chrisger]

Hi,

sorry for my overshoot...

i once used DevStud to chance ressources of a standard app, never with a labView app. should have tested it before submitting the post!
Well, there's a tool "Resource Hacker" or "ResHack". maybe thats a solution.

best regards
chris

[tst]

Try looking at OpenG builder. I never tried it but it's possible it has this feature. Even if it doesn't, OpenG is modular and open to user requests, so if they'll respond, it will probably be faster than NI.

[red-ant]

Hi chris,

ResHack is able to correctly add VERSIONINFO ressource to a LV-app built by ApplicationBuilder.
So now we have the first approved workaround for our big goal 🙂

But this is no final solution since nothing can be automated. Errors in usage are predicted.

We are right now experimenting with OpenG Builder...
Results to come.

Best regards,
Oliver Thost.
red-ant measurement technologies and services

[chrisger]

Hi there

ResHack can be run from the commandline! You should be able to create a script for adding the VERSIONINFO.

best regrads & let us knwo
chris