Before I say anything, let’s consider the following dialogs.
“Hey Bob, what are the changes that you made to this file?”
“Willis, the class that you coded earlier is lost. Please write it again”
“John, your code just stopped working. It was working fine before. Did anybody modify anything?”
These are few of quite common reactions one gets when working in a team. When you are working in any development project, it’s possible that more than one developer is working on the same file at a given time or you need to release different versions of a product which causes the development of the subsequent version as well as maintenance of last released version to take place simultaneously. You may not wish to release the new features with old versions. And so you need to keep both the versions of the product separate. For all these problems, Source Versioning is the solution.
Source Versioning is one of the most important aspects of software development life cycle. It’s a process where changes to the project files are analyzed and multiple versions of the files are kept in a central repository.
There are many different Source Versioning systems are available out there. Few of the most used are <a>Apache Subversion a.k.a. SVN</a> for linux/unix world, <a> Microsoft Visual Source Safe</a> for Windows world and <a href=’’>Rational ClearCase</a> (both).
In this tutorial, I am going to show you how you can configure your local windows machine as a subversion server. The tutorial will give you step by step instructions to install & configure VisualSVN, the windows equivalent of Apache Subversion.
First you need the latest version of VisualSVN. So download it from its official website <a>here<a/>. I am installing the latest version at the time of writing 2.5.1, but other versions should be similar.
Execute the installer & follow the on screen instructions. The following snapshots show the various screens.
One completed, setup the server configuration. Though default settings are fine, it’s better to use a different port number to avoid any conflicts in case you are running any other web server that is using 8080 or 80 as default port. I use 300 as a default port for svn however feel free to choose any other random number that is not being used by any other application.
The next step is to create a new repository. A repository a space on your hard disk that will store all the versions of the file and the Meta information about those versions like author, date saved and any comment that you may add as an explanation for that version. Just right click on the Repositories node on the VisualSVN Server Management console and click New>Repository…. Give your repository a name. Though not necessary, you may wish to check the Create Default Structure (Trunk, Branches, Tags) to automatically generate well known three folder structure.
That’s all. You now have a source versioning server running. Other computers on your network may access the server at <your-computer-name>:<port>/svn/<repository name>.
To see how to make use of source versioning in Visual Studio, click here.
To see how to make use of source versioning in Dreamweaver, click here. The article uses Mac but similar process can be used for windows as well.