[mapguide-internals] RE: File versions...

[Trevor Wekel]

I need to start looking at build automation again.  It should be possible to increment the file versions with every build.  We could start at build 1 for each new release and increment the "build number" before each build is performed. The build number would be stored as a file in subversion.

I liked the SVN revision idea but what happens when we hit 65,000 revisions?


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Walt Welton-Lair
Sent: Friday, March 13, 2009 3:32 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: File versions...

I think it would be worthwhile to update the major & minor values each release.

There's a freeware tool called StampVer (http://www.elphin.com/products/stampver.html) which can be used to set version information in DLLs / EXEs.  But it doesn't work on 64-bit modules.

Walt


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Friday, March 13, 2009 4:59 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] File versions...

Hi all,

Looking at the code, the .rc files generally do not reflect the current
MapGuide version number.

Is it worth maintaining these manually to keep in sync with at least the
current release major version?

Is there a utility that can be run post-build to update the file
versions embedded in .dlls (and exes?) to reflect something like the
MapGuide version number + SVN revision? (2.1.0.3728)

Jason
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals