TFS vs SVN [closed]

Answer 1

I'd pick SVN. I've worked with SVN from a developer standpoint before and I currently work with TFS, and let me tell you that TFS is painful. While TFS is feature full and is more than just version control, its version control is sloppy at best. Merging is horrendous and many of us now turn to manual merging or merge tools because we can't rely on TFS. Files go missing, aren't downloaded to the local system sometimes, and there are just oddities in its behavior that make you want to bang your head against a desk.

That being said, if you want TFS in all its glory, are willing to work with its pain points, it is a great tool to setup automated builds, and releases.

Answer 2

TFS can import from SVN, however SVN cannot import from TFS. So if you don’t find a good reason otherwise use SVN, as it is easier to change your mind later.

One of the best things about SVN is that every source code control system I know of can import from it, so choosing SVN us a very low risk option.

Answer 3

Pros:

• Integration with Visual Studio. A real plus if you're leveraging a full Microsoft tech. stack for development.
• Automated builds (though achievable via other products) is really nicely done. Continuous Integration and Gated check-in builds are fantastic IMO.

Cons:

• Windows Workflow Foundation. For some reason, Windows Workflow Foundation was chosen as the method to customize many aspects of TFS. In short, you need a book on Windows Workflow to understand it, and I simply don't have the time. Very disappointing IMO.
• Project Management. The concept of work items is simple enough I guess, but there's a lot of oddities with it that just leave me flummoxed. It's just way too complicated IMO. Coming from a Trac + SVN background, I much prefer Trac here. Again, just my opinion.

Answer 4

It's been 1.5 years now that I'm using SVN for various projects. Setups I've used so far:

• AnkhSVN client for Visual Studio. It integrates nicely as Source Control provider since version 2.
• Servers either CollabNet Subversion on windows or Apache 2.2 with SSL + SVN through DAV on linux.

Haven't had any problems with any of these setups and I definetly recommend using SVN as it's free and easy to start using. Also many project management / bug tracking packages integrate with SVN (like trac for instance).

Answer 5

I'd say TFS is more than just source control. If you can afford it, I would definitely advise to use it. When you start using Team Builds for example, or using stuff like Work Items, then you'll see that TFS can really manage your whole development life cycle, providing a rich environment in which reporting, ease of use, slick VS integration and solid source control are all rolled in to one.

It does require some iron on the server side. I do not find it to be slow however, it works nicely over VPN and supports offline work.

A major con is the install process (on the server side) which is tedious, non-flexible and in my mind (I come from a field in which packaging up apps and deployment are very important) a bad example of how SQL Server, Reporting Services, Sharepoint and webservices could be installed.

Answer 6

In my experience SVN overall is far quicker and more painless. I've used it with XCOPY deployment scripts that allow you to work and deploy far faster overall in comparison to TFS.