NAnt (or nant contrib) has a build task that will generate a CommonAssemblyInfo file which you can then reference (as a link) in all your projects. Then you can have each assemblyinfo file in the project have a description and title but leave out the version number and any other settings that are common to all the projects (e.g. copyright).
Here's info on getting it working with CCNET http://igloocoder.com/archive/2008/01/04/versioning-applications-using-nant-and-cruisecontrol.net.aspx On Fri, Feb 5, 2010 at 1:39 PM, silky <[email protected]> wrote: > On Fri, Feb 5, 2010 at 1:33 PM, Bec Carter <[email protected]> wrote: > > TGIF! > > > > What assembly versioning convention do people here follow? I assume > > theres a Microsoft standard that I havent found yet. > > I'm yet to get fully into this (but I'm getting close). What I've > implemented at home (on dashy) is > > major.minor.build.revision > > So the download file generated is in the form of: > > filename-0.0.463.1263.zip > > Thus it hasn't made it to a first version yet, but has had quite a few > builds and significant commits against the repo. > > Of course, it's all auto-generated (which is the point, and awesome, and > fun). > > CruiseControl.NET can easily push through the build number, and I > assume Hudson can as well (I'm moving to that at for my CI server > now), but it should go without saying that this structure will imply a > significantly different build number if you switch build servers > mid-project (i.e. you may need to set a 'base' build number once, > after doing the switch, just to make sure it all matches up). > > That said, with this version I haven't put it to the "test" of using > it for any decision-making in-code. But nevertheless, it's what I use, > and I quite like it. > > > > Cheers > > Bec > > -- > silky > http://www.mirios.com.au/ > http://island.mirios.com.au/t/rigby+random+20 > > paean-KLEPTOMANIAC mousiness heckle. >
