• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 538
  • Last Modified:

What steps need to be taken to complete the task of moving source code from SVN to Team Foundation server

Can someone please help me put together a process summary of what steps need to be taken to complete the task of moving the Visual Studio .NET based application and SQL Server database/SSIS code from Subversion (SVN) to Team Foundation server (TFS)? Is this a good idea?

Also any comparison matrix between the characteristics, pros and cons of the two would be highly appreciated
0
skaleem1
Asked:
skaleem1
1 Solution
 
StephanLead Software EngineerCommented:
I think the primary question you can ask yourself is
- What kind of tech will be primarily used by the company? Is it more that .NET, keep SVN
- Do I want to pay that much for it? If you have a Microsoft Partnership, you don't have to.

The big thing about TFS is that it can integrate with various platforms that Microsoft have available.
- SharePoint for the project documentation
- Build agents for Continous Integration and Continous Delivery.
- IDE integration on Visual Studio (yes, it is also possible on

Also TFS has the capability to keep the work directly to the source code, so it is much easier to couple your code with the work you have done that is written in a work item.

Maybe take a look at Team Foundation Service, or now called Visual Studio Online. You can try it out with max. 5 users for free and it will show you the most things you can do.

There are some articles around that will match the TFS vs Subversion, take a look at those:
http://nakedalm.com/tfs-vs-subversion-fact-check/ (it's a bit old article because they talk about VS2010 and TFS 2010)
http://www.thecodeconnection.com/2010/06/team-foundation-server-vs-subversion.html
http://blog.bsktcase.com/2012/07/12/tfs-v-svn-2012-update/

Also take a look at GIT. It is a more mature version compared to the versioning tools like SVN or TFS
0
 
skaleem1Author Commented:
Thanks a lot
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now