As anyone that reads this blog should realise (that’s if anyone is actually reading it, comment people please!), I am a Applications Developer. I work for a large law firm writing Visual Basic .NET applications, along with a fair amount of SQL work. However I also do a lot of personal development outside of work, building websites and applications for private contracts. I wanted a similar Source Control solution to the one that we use at work (Source Gear’s SourceVault), but I wanted one extra feature!! Distributed Source Control!
For those that are not 100% on what Source Control is here is a little explanation. Source Control systems are designed to keep a historical copy of your source files; whether they be source code, websites or even documentation. The crux of the matter is you “check” files in and out of the repository (the source control container), most systems also give you the option of tagging comments to your “check ins” so that you can remember what changes you made to your code!! The whole purpose of a SourceControl solution is to save you from disaster when it all goes wrong! Should you make a change that breaks your application, or need to roll back when the plan changes, you can simply pull out an historical copy of your file from a previous check in!
The other major benefit of Source Control systems is that they allow for collaboration between multiple developers. When Developer A checks out a source file to work on, the repository allows Developer B to access the file but it prevents him from checking the change in until Developer A has finished with the file. Once both Developer A and B have both finished with the files, the repository offers to merge the changes together. Some Source Control solutions store the details and content of the source files in an SQL database (as SourceVault does), however the tradition is to use a file structure (like SubVersion and Microsoft’s SourceSafe).
My custom SourceControl solution is SubVersion and Dropbox running on Windows 7!! Read More for instructions on how to re-create it!




