[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: C# AssemblyInfo integration

From: Aaron Friesen <aaron_at_cartopac.com>
Date: Fri, 28 Aug 2009 18:12:03 -0400

> -----Original Message-----
> From: Yves Goergen [mailto:nospam.list_at_unclassified.de]
> On 28.08.2009 18:48 CE(S)T, Andy Levy wrote:
> > On Fri, Aug 28, 2009 at 12:45, Yves
> Goergen<nospam.list_at_unclassified.de> wrote:
> >> On 28.08.2009 08:11 CE(S)T, Yves Goergen wrote:
> >> Is that by intent that keywords are not updated if the file didn't
> >> change? How is something like $Revision$ meant to be useful if it
> >> doesn't reflect the revision?!
> >
> > $Revision$ reflects that last revision in which *that file* changed.
> > It's very useful for keeping track of individual source files.
> Damn, so how can I get the latest revision of the project into a
> constant file at all? There's no file that is always changed.
> I don't like the idea of running a separate svn client because 1) it
> needs to be installed on every PC and 2) it needs to authenticate
> separately from AnkhSVN, the Visual-Studio-integrated tool.

Our build setup has a project specific assemblyinfo file and a
global one that contains only the revision pieces. Each project has
a pre-build step that checks for the existence of the global one.
If it does not exist, the default template is copied into place.
The template has a revision number of 65534. This lets us know
that a particular project was built on a developer's system, not
the build system.

The build system, prior to building any projects, creates a version-
specific global assemblyinfo file that contains the version number
of the build. The version number for the build is taken from the
output of svnversion. Mixed revs are not an issue on our build

Works for us.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-29 00:13:07 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.