Hi Tim,
What I've seen until today is that most people use the AssemblyInfo.cs
AssemblyVersion attribute for that purpose, the natural way of handling
(assemblies) versions in .net. That's relevant only if you build .Net
project with NAnt of course, I assumed you are in that case.
I'm starting to add versioning to my build process; what I do is
basically get the assembly version which has been built, using
${assembly::get-version('myassembly.dll')}. There are others functions
such as version::get-build, version::get-major etc if required as well.
I'm sure you've read this already, but just in case :
http://nant.sourceforge.net/nightly/help/functions/assembly.get-version.
html
http://nant.sourceforge.net/nightly/help/functions/index.html#Version
For the moment what we do is let the developer in charge of release
modify the AssemblyInfo.cs file and especially the AssemblyVersion
attribute to whatever required, go through the publication process and
label in VCM (for later rebuild if required) with the same version
number if the publication was successful (those steps are quite
automated).
Once it's robust and well accepted by people, I'll switch to
"semi-automatic", which is : at each automatic build (continuous
integration), modify AssemblyInfo.cs automatically (increment the last
version number probably), checkin and label in VCM.
About incrementing it automatically, and versions in general, here are
the links I've kept under my hand for the moment :
http://code.mattgriffith.net/UpdateVersion/
http://blogs.biasecurities.com/jim/archive/2004/02/19/348.aspx
http://weblogs.asp.net/sjoseph/archive/2004/02/19/76277.aspx
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/h
tml/tdlg_ch5.asp
Suzanne cook's blog :
http://blogs.msdn.com/suzcook/archive/2003/05/29/57148.aspx
Hope this helps and that I'm not totally out of focus :)
I'd like to hear from other people who are managing versions as well.
Thibaut
http://blogs.dotnetguru.org/tbarrere
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim Mavers
Sent: mercredi 4 août 2004 16:56
To: [EMAIL PROTECTED]
Subject: [Nant-users] Auto incrementing build numbers
Is there a way for nant to create (and keep track of) build numbers? I
have
created special targets that build specific releases of our code which
needs
to be labeled. I would like to be able to simply increment a build
number
and use that through the nant xml build file.
I checked Ant, and it has a PropertyFile which allows you to create a
file
for storing build numbers, but I don't see this in nAnt.
Has anyone done this before?
Thanks,
_________________________________________________________________
Planning a family vacation? Check out the MSN Family Travel guide!
http://dollar.msn.com
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
