Search code examples
visual-studiosvnversion-controlplasticscm

Plastic SCM vs. SVN


I'm currently researching new source control options for a team of 10 developers. We do .net development in Visual Studio 2008. We currently use VSS for source control.

We are looking for a centralized source control solution(non-distributed), with a nice Visual Studio plugin. My manager has recommended Plastic SCM and I've always heard good things about Subversion. I'm trying to decide if we should adopt Subversion or Plastic SCM.

There isn't much information out there about Plastic SCM (except what they've written) and I was wondering if it would be a good solution. They make it sound as if branching is much simpler.

Subversion on the other hand has a robust, mature community, and it has been thoroughly field tested.

What are the pros and cons to these tools?

Also are there any other tools that you could suggest?

Thanks


Solution

  • I haven't used Plastic SCM before, but Subversion worked very well for me in the past. If you're not bound to a free solution like SVN, you might consider Team Foundation Server. Beside Version Control, TFS offers additional nice features like work item tracking, integrated reporting ... As you can imagine, the Visual Studio integration is just great :)