Question

I have an asp.net/C# app that uses subversion for source control.

My app automatically increases it’s AssembleVersion and AssemblyFileVersion on each build which works like a charm, and displays the build number in the administration side of the site.

We keep track of AssembleVersion and AssemblyFileVersion’s when we do deployment, however, when an issue arises and we need to roll back to a certain version, we have no idea which revision to target in subversion.

I have few ideas:

1. Save AssembleVersion as comment in each file
2. Have a keyword in commit comments that get’s replaced by AssembleVersion on each commit(still need to figure out how to do it)

Any help and suggestions will be appreciated

Updated:
option “1” is actually a stupid idea,cause this will mean that everytime i build, all files will be marked as updated and when i commit, every single file will be updated

Answer 1

When I build, I put that build number everywhere.

• I put it in a tag in svn.
• I put it in the Assembly metadata of every assembly I build.
• I append it to the end of the filename in my installers.
• I put it in the footer of each of my deployed webpages.
• I put it in the footer of my reports.
• I put it in the splash screen of my client side apps.
• I put it in the welcome screen for my installers.

The only thing I don’t put it in is my coffee, which I take black.

All of this lets a maintainer know at a glance exactly where the code came from for what they’re seeing, whether they’re viewing a webpage, or looking at the properties of one of the built assemblies in Explorer, or whatever.