+1. This currently throws a warning "Assembly generation -- The version '1.0.1.27/1dd3-master build 6' specified for the 'product version' is not in the normal 'major.minor.build.revision' format" but it seems that the warning is removed in .net 4.0: http://bit.ly/aWIYeX
On Jan 29, 11:45 am, Andre Loker <[email protected]> wrote: > On 29 Jan., 01:58, Mauricio Scheffer <[email protected]> > wrote: > > > Which brings up another issue: how do we build AssemblyInfo files now? > > AFAIK there is no clean way to embed the sha1 in the assembly version. > > I suggest we use something like Daniel shows > > inhttp://www.tigraine.at/2009/10/27/simplifying-releases-through-git/, > > but we would also use the "number of commits after tag" part. > > Personally, I build my version numbers as follows: > > AssemblyVersion: major.minor.revision.commit_count > Example: AssemblyVersion("1.0.1.27") > > AssemblyInformationalVersion: major.minor.revision.commit_count/ > shorthash-branch build_number > Example: AssemblyInformationalVersion("1.0.1.27/1dd3-master build 6") > > Where > major.minor.revision are set manually > commit_count is the total number of commits on the current branch, > which can be determined by: git rev-list HEAD | wc -l > shorthash are the first 4 characters of the commit hash > build_number is the sequential build number as provided by e.g. CCNet > > See my rake buildscript for details:http://github.com/aloker/dotnet-raketools -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
