Quote:
|
VB6 is more of a pain since it only allows you to update the first, second, and fourth version values. To update the third value, you need to update the executable's version resource after building.[/B]
|
There is another solution, which we are using in our build process:
vbAdvance (click to go to the site - Kinook, why are links on this site the same colour as text?! 
) allows you to build VB6 projects with a give four part version number.
I use a subroutine to write the revision number into the project file with WriteINI, prior to building it with the standard VB6 build step with the version number set as VB expects (Major.Minor.Build). I then replaced my VB6 build steps with calls to this subroutine.
The final files then have "Major.Minor.Revision.Build" format versions.