Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Sat, 30 Mar 2002 10:43:40 +0000 (UTC), Tony Hoyle <tmh at nothing-on.tv> wrote: >Bo Berglund wrote: > >> And the build really does not need any letters, why not simply >> increment the number (to 58 in this case) each time a build is done? >> >58 was a development build. I forgot to leave a gap, so we're stuck with >letters for the release builds. > >Tony > Now I have actually located the problem with the lacking file version info in cvs.exe (and in the cvsservice.exe and cvsnt.cpl as well): The following needs to be done: In version_fu.h the following line is added at the end (in one line, newsreader wraps into two lines): #define CVSNT_FILEVERSION CVSNT_PRODUCT_MAJOR,CVSNT_PRODUCT_MINOR,CVSNT_PRODUCT_PATCHLEVEL,CVSNT_PRODUCT_RELEASE In cvsnt.rc2, cvsservice.rc2, cvsntcpl.rc2 add this line immediately after the VS_VERSION_INFO VERSIONINFO line: FILEVERSION CVSNT_FILEVERSION Now build and you will notice how the file version number comes up in the Version properties pane of the files: 1.11.1.3 To see the build number one has to go to the File Version in the strings section and it looks like before: Cvs NT 1.11.1.3 (Build 57b) I suggest this is included in the source tree. Unfortunately I don't know how to make "patch" files so I can't send that, but the above edits are not so difficult really. /Bo (Bo Berglund, developer in Sweden) _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs