Having used Team Foundation Systems (TFS) for many years I grew accustom to having an automated build process and the ability to have the Revision number in my binary file versions. Recently I began work for a client that used SubVersion as their source control system. This removed much of the niceties I was used to having in other TFS based projects. I set out on a search of the internet and found a couple methods to provide similar functionality of tying a deployed package of code back to a revision in my source control.
Both of these methods require that you use the Tortoise SVN tool and have it installed on your local system. Since both of these methods do not require you to actually log into SVN to get the revision number, it is important to note that the revision number displayed will reflect the Revision Number of the source code on your local file system. That is to say, that if you don’t “Update” prior to building, you will have the Revision Number from the last time you updated.