Quoting "Bryan D. Andrews" <bandrews@trendcore.com>:
> I am trying to come up with a way to have our revision number and our
> revision on our assemblyinfo.
>
> I have found a few posts on getting the head revision, but I am unclear
> if anyone is doing it this way:
>
> I want to commit and as I am committing write the revision number to the
> assemblyinfo just before it commits so our entire team has a build
> associated with the revision clearly.
Hi Bryan,
I am pretty sure I understand what you want to accomplish. I wanted to do
the same thing. You are going about it the wrong way. Here is the right way.
1. Do you development work (for example) in trunk. When you are ready
to "version" your software, set the version number of your assembly in
the assemblyinfo file. Now, when you are happy, make your final commit
to trunk. *Note* the revision number of that final commit; it is very
important.
2. At this point, revision X of trunk lines up with the version you
defined in the assembly info.
3. Make a tag of your trunk, and you *must* make the tag for that
particular revision to ensure that you are getting what you expect. 4.
At this point, folks that want to use V1.0.1 of your assembly will
either checkout or export tag V1.0.1 of that library when they want to
use it.
What that helpful?
If you want to talk to me more about it off the list I would be happy
to. We manage versioning of about 50 .NET dlls using Subversion right
now. I would be happy to talk to someone else about it!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 11 14:38:53 2006