Insert SVN version and Build number in your C# AssemblyInfo file

Software version number is quite important. It helps you track what versions have your users when they report something. And when it’s linked to an SVN version number, it’s even better.

Well, with MSBuild Community Task, you can easily automatically generate smart version numbers, you have to:

  • Download MSBuildCommunityTasks
  • Make sure your “svn.exe” binary is in C:\program files\subversion\bin
  • Add this at the end of your .csproject file :

2011-07-02 update: As given in Markus comment, this code is a much better option:

1
2
3
4
5
6
7
8
9
10
11
12
13
<!-- Import of the MSBuildCommunityTask targets -->
<Import Project="$(MSBuildExtensionsPath)\MSBuildCommunityTasks\MSBuild.Community.Tasks.Targets" />
 
  <!-- to AssemblyInfo to include svn revision number -->
<Target Name="BeforeBuild">
	<SvnVersion LocalPath="$(MSBuildProjectDirectory)" ToolPath="$(ProgramFiles)\VisualSVN\bin">
	   <Output TaskParameter="Revision" PropertyName="Revision" />
        </SvnVersion>
 
	<FileUpdate Files="Properties\AssemblyInfo.cs"
                Regex="(\d+)\.(\d+)\.(\d+)\.(\d+)"
                ReplacementText="$1.$2.$3.$(Revision)" />
</Target

You should only have a “</Project>” field left…

Then, you just have to open your project and build your project, it will fail once (missing version.txt file) and then work forever. This will generate your Assembly & AssemblyFile versions like this: Major.Minor.SvnVersion.BuildVersion

In your C# code, to get your version, you just have to add something like that:

1
2
3
4
5
public static String Version {
  get {
    return System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.ToString();
  }
}

19 thoughts on “Insert SVN version and Build number in your C# AssemblyInfo file”

    1. The easiest way I could find is to add a condition on the SvnVersion tag :

      1
      
          <SvnVersion LocalPath="$(MSBuildProjectDirectory)" Condition="Exists('$(ProgramFiles)\subversion\bin\svn.exe')">

      Your build number will be incremented and your SVN revision number won’t be fetched.

  1. Thanks, just what I was looking for!
    I made a little change on configuration because my SVN binaries are located elsewhere.

    1
    
    <SvnVersion LocalPath="$(MSBuildProjectDirectory)" ToolPath="$(ProgramFiles)\CollabNet Subversion Client">
  2. Interesting. But what do you do if the svn revision number goes over 65535 (i.e. the maximum for any of the 4 version number components) ?

  3. Most of the people of my blog are coming for this post. I should really find a better solution. Something between the solution of “theKindOfMe” and mine.

    It would be great to extract build number and svn revision number and just update the AssemblyVersion file without having to specify each property in the “csproj” file.

    I should work on a clean solution to that problem. But that really isn’t fun to do because MSBuild XML language is not really comfortable.

  4. Hello, can you tell me which changes can be done to get the same for “*.vcproj” project file.
    Tx in advance !

  5. The .vcproj files don’t use the MSBuild format until Visual Studio 2010. And then my guess is that you can pretty much use the MSBuild vcproj file the same way.
    I haven’t tested it because the only C++ I do is on Linux with some Makefile files.

  6. But is a possibility to use versioning on the .vcproj projects? For instance i have a .dll created in .vcproj project and i want to have versioning on it.

  7. Hi, i’m trying to using this system.
    i have a little problem. I try to change (from visual studio propertyes interface) minor and minor version.
    i put the version to 1.1.svn.build.
    When i run my application the version come back to 1.0.svn.build. How i can change the major and minor version?
    Thank’s a lot and sorry for my english

  8. Note: This works but when you run the command, the version.txt file won’t contain your svn version. It just increments.

    To check everything is working, go look at your AssemblyInfo.cs file. It should have the right svn number (it just won’t match what the version.txt file says).

    This through me for a loop at first. Thought it might others as well.

    Thanks for sharing however. Great solution. Cheers

  9. Hi

    Sould not be the Revisionnumber: ActualRevision +1.
    If the actual number is 400. And you check in the number is 401. But in the AssemblyVersion there is still the number 400.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>