For example, [assembly: Assembly Version("184.108.40.206")] indicates 2 as the major version, 3 as the minor version, 25 as the build number, and 1 as the revision number.
A version number such as [assembly: Assembly Version("1.2.")] specifies 1 as the major version, 2 as the minor version, and accepts the default build and revision numbers.
I would prefer to call msbuild from the commandline itself and not create another msbuild scripted file. For example look for the line that starts: "[assembly: Assembly Version" and replace it with something else.
However, if you don't have much in your Assembly (and remember you can split the Assembly into multiple cs files if you want) I'd suggest creating the file from scratch with a couple of echo statements.
This is the kind of thing I would have used Perl to do, in the past. [ 23 April 2008 – 1150am PST – I updated the script to deal with the Assembly files in a VB project, and also to deal with version numbers that have less than 4 digits. ] Set Version.ps1 # # Set the version in all the Assembly or Assembly files in any subdirectory.
When distributing a library you often run up against versioning problems, once facet of which is simply determining which version of that library your client is running.
A version number such as [assembly: Assembly Version("1.2.15.*")] specifies 1 as the major version, 2 as the minor version, 15 as the build number, and accepts the default revision number. The default revision number is the number of seconds since midnight local time (without taking into account time zone adjustments for daylight saving time), divided by 2.
As I am not able to write any code inside , how will I update the value of Assembly File Version.
Create a new solution-level file (I usually create a Build/ folder in the solution root, but anywhere reachable by all your projects will do) called Common Assembly
In here you can put any information common to all your assemblies, including the version number.
Get Info(repo URI, out info); [assembly: Assembly Version("220.127.116.11")] [assembly: Assembly File Version(String. You can create MS Build task for the same: see There is command line utility (Sub WCRev) that can also be used for keyword based replacement ($WCREV$ for revision) - see the example here: SVN_en/Finally, you can probably roll out your custom code (doing regex search/replace) to do the same which some (including me) has done - see one such example here: If I remember correctly, while installing Tortoise SVN, you have to select command line client tools for installation (run the installer again to get them).
Or else you can always download svn command line client.