irobisnon
(Ian Robinson)
January 9, 2008, 2:51am
1
Hi
Im using the Compile VB6 project action, and using a VB Version Property set.
When the exe is compiled and i use the property set to assign the verison number the fileversion of the exe results in
Majorversion.Minorverison .0. Releaseversion
But the Fileverison in the FileInformation results in Majorversion.Minorverison.Releaseversion ( although it is padded to couple of zeros)
Is this a fault? What results is that the "File Version" of the exe never matchs File Version information ?
Is there a work around as there is no way to set the fileverison via scripting.
regards
Ian robinson
tate
(Tate Needham)
January 10, 2008, 6:57am
2
Hi Ian, I think this is how VB6 is supposed to work. I created a new VB project, set version info to Major: 1, Minor: 2, and Release: 3, and then did a File | Make, the version info that Windows reported was: File Version (at top of properties): 1.2.0.3 File Version and Product Version (in the Other version information section): 1.02.0003 cheers, tate.
irobisnon
(Ian Robinson)
January 11, 2008, 3:21am
3
Thats what im talking about. Why do they not have revision number as the 3 number as per the order in the project properties? Or at least show a “0” that you cant edit. Go figure! Maybe there is something on MS website /resource compiler. ill post back if i find something