Friday, December 30, 2011

Working with Subversion and VS


Working with Subversion and Visual Studio: 


Introduction:

This article demonstrates how to install/configure the open source version control “Subversion” which we can integrate and work in VS 2008. This article starts with installation steps of SubVersion. After that, will expain how we can integrate with Visual studio and some basic functionalities of SubVersion.  
Installation Steps:


.I have installed the subversion exe “AnkhSvn-2.3.10509.1073” which is installed as plugin in Visual studio and for managing the repositories(Similar to work space in TFS).


 Download Link

Step2:


After that install UI tool “TortoiseSVN”.TortoiseSVN is an easy-to-use SCM / source control software for Microsoft Windows.


TortoiseSVN Download Link

Step3:


After installed both the things, we need to choose the source control as subversion instead of TFS in visual studio:


In VS menu -> Tools ->option -->Select SubVersion option



Step4:


There is some difference when compared to TFS , in TFS we first create workspace , in Subversion we’ll create the repositories by just right click the folder and select TortoiseSVN->Create repository here as showed in below.


Step5:


By default, subversion repositories have their own folder structure, first it’ll ask you to create that structure:


Step6:


Once we created the repositories we need to add our files to it. To add the files Right Click the Solution in Visual Studio and choose the options:·
  • · Add Solution to Subversion
  • · Add Selected Projects to Subversion



Once the files has been added the in repositories, we can the files in the attached repositories as shown below:



The check-in/check-out is different from TFS, here in subversion check-in will call it as “Commit” and symbols also changed , we’ll see green tick for check-in and red tick for check-out.


Get latest to specific version, we have the below option as compared to TFS:


Summary:


Using SubVersion source control has some advantages over TFS and will try to use it see the differences.
  • First its free of cost – open source version control·
  • Easy to install and use component , support for visual studio·
  • Ready to setup our own version control system.