LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why doesn't the exe file made by Build reflect the version number of the vi used to make it???

The verion # of the exe is always 0 so it is hard to track the level of modifcations.
0 Kudos
Message 1 of 10
(3,759 Views)
Hi,

Unfortunately the version of executables are kept track of separately from the actual version number of the VI. Executable version number is kept track of in the Application Builder >> Installer >> Properties >> Product Version Number. The VI version number is kept track of in the VI Properties >> Revision History. If you are using the VI Server property for the VI and getting the History:Revision History property, this will display the revision information that is saved in the VI properties and not for the executable. However, you can set the product version number in the Application Builder as mentioned above.
0 Kudos
Message 2 of 10
(3,757 Views)
I wouldn't want the version of my exe to be the same as the version of the main VI anyway. The VI may undergo numerous revisions in the developement mode before building it and when released, I wouldn't want the exe to be at rev 39 for example. I would want it at rev 1.0. Then there's the problem of changing a subVI but not the main. If the exe version reflected the main VI version, the rev wouldn't change at all.
0 Kudos
Message 3 of 10
(3,757 Views)
But I should be able to get the Version Number of the build specification inside the LabView code to display it in a "about" dialog. How can I do this?
0 Kudos
Message 4 of 10
(3,497 Views)
Open a reference to your VI, wire that reference into a property node (or simply drop a property node and change its class to the VI class) and read the VI's History>>Revision Number property, which you can now display.

___________________
Try to take over the world!
0 Kudos
Message 5 of 10
(3,493 Views)
Thats not what I meant. That way I am getting the revision Number of the VI, in my case 495, what I want to get is the Version Number the "Build application" of LabView 8 is increasing automatically, eg 0.1.4.0
0 Kudos
Message 6 of 10
(3,484 Views)
Unfortunately the application builder does not contain a location to enter a version number.  I would like to see this feature also.  You could build an About.vi and manually change it every time you make a change and recompile.  If you create an installer on the application builder, click on the Properties box and you will see a place to enter the version number.  But I think this is the version of the installer, not the application.  This may still be usable but I don't know how to retrieve this info programatically.
 

Message Edited by tbob on 05-08-2007 10:42 AM

- tbob

Inventor of the WORM Global
0 Kudos
Message 7 of 10
(3,469 Views)

tbob, the 8.x app builder does have the option of having a version for the executable.

I don't think this is exposed anywhere in the VI server hierarchy, and it might even be a Windows only thing, as I believe this uses the standard Windows way of identifying the version number.

You can use Windows API functions or .NET to get that version number. Try looking here for an example.


___________________
Try to take over the world!
0 Kudos
Message 8 of 10
(3,459 Views)
Although I have 8.2 installed, I use 7.1.1 mainly.  The picture I showed is from the 7.1.1 app builder.  I'm glad to hear that 8.x has this feature.  Sooner or later we are going to migrate to the latest version and I'll start using it rather than just play with it.
- tbob

Inventor of the WORM Global
0 Kudos
Message 9 of 10
(3,456 Views)
I tried to give out the internal VI-version number, in the compiled program its zero again.
If you open the compiled program in an editor, you can find the information you edited in the build at the end of the file. Its in unicode, so if you want to search for a string, you have to insert spaces after each letter:
"test" => "t e s t"
But still I don`t know how to access this information...

But thank you for your replys!!!
0 Kudos
Message 10 of 10
(3,437 Views)