Re: Updating the AssemblyVersion attribute from CCNet

How does everyone currently support versioning with the devenv builder?  


On Sat, 6 Nov 2004 12:39:19 +1300, Mike Roberts
<mike.b.roberts-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
> Somebody mentioned the other day that it would be nice to link to NAnt
> tasks within a CCNet project - I'm not sure what the licensing
> implications of this are since NAnt is GPL (with an exception I don't
> really understand), but this might be a good implementation for this,
> something like:
> 
> <tasks>
>    <nantTask nantTaskType="Nant.Tasks.AsmInfo">
>        <!-- some way of passing in NAnt params that would be tied up
> reflectively -->
>    </nantTask>
> </tasks>
> 
> Of course, this might be hard to implement, never mind the licensing
> constraints.
> 
> I don't actually think CCNet *needs* this kind of thing (it might be
> 'nice to have'), mostly since in a year or so's time everyone who
> doesn't use NAnt will be using .NET 2 and Msbuild, which can do this
> for them.
> 
> re: plugin DLLs - I don't know where Owen was up to on this.
> 
> Mike
> 
> On Fri, 5 Nov 2004 11:07:59 +0100, Thibaut Barrère
> 
> 
> <thibaut.barrere-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
> > Hi,
> >
> > I have an idea of feature for ccnet and would like your opinion : a
> > plugin or task of some kind which would update the assembly version
> > attribute in source code.
> >
> > To illustrate, today I use a NAnt task for that :
> >
> > <updateversion major="-1" minor="-1" build="${build.number}" revision="-1">
> >         <fileset basedir="${path::get-directory-name(solutionFile)}">
> >                 <include name="**/AssemblyInfo.cs"/>
> >                 <include name="**/CommonAssemblyInfo.cs"/>
> >                 <include name="**/AssemblyInfo.cpp"/>
> >         </fileset>
> > </updateversion>
> >
> > The behavior is rather obvious, except "-1" which means "do not
> > change". As well, it can handle c++ files. The implementation relies
> > on a regex match/replace.
> >
> > Sure I can keep this in my NAnt build like today, but I'd personally
> > push to integrate some built-in mechanism in CCNet to ease version
> > increment (which would then be available for any builder, including
> > devenv builder).
> >
> > My first idea was that it was maybe "overfeatured", but I realized
> > that many people learn all this the hard way.
> >
> > what do you think ?
> >
> > regards
> >
> > Thibaut
> >
> > ps : this bring another question : is there more details or inner
> > thoughts about the plugin model Owen evoked a couple of weeks ago ?
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_idU88&alloc_id065&opclick
> 
> 
> _______________________________________________
> Ccnet-devel mailing list
> Ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click