Geeks With Blogs
AngelEyes on .Net Tips, tricks and WTFs about Asp .Net, SQL Server and the likes.

This post is for someone who's like me, i.e., has never used Sebversion before, and the documentation, although there's certainly plenty of it, doesn't really follow the KISS principle.


* Subversion - the version control software.

* TortoiseSVN - GUI for Windows Explorer (not IE)

* AnkhSVN - Add-in that enables the use of Subversion directly from Visual Studio

* SVNService - Runs the Subversion "daemon" as a Service in Windows, on the Server side.


Branches, Tags and Trunk:

* Tagging: You might tag your project when you reach Version 1.0. Then you can go on making changes to your project, but if you need to get back to Version 1.0, you can always use the tagged version of your project to retrieve all the source files exactly as they looked when your reached Version 1.0.

* Branching: If you are working on a project, and want to try some experiments, but you aren't sure you want to keep them, then you can branch the project. After branching, you will have two copies of your project: the main trunk, and the branched version. Work can then continue on both the main trunk, and the branch. Changes to the branch will not be seen in the main trunk, and changes to the trunk will not appear in the branch. Both branches of the code will have acecss to any changes that occurred before the project was branched. As I will explain below, branching is handled in a way to insure that only a minimum amount of server side disk space will be used.


I found a very usefull article here

Posted on Saturday, July 22, 2006 11:32 PM | Back to top

Comments on this post: Trying to understand Subversion

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © AngelEyes | Powered by: