TFS – Does It Suck?

You may also like...

4 Responses

  1. Brad says:

    Haters gonna hate. I have used TFS for a while. It has a few flaws on the source control side (offline mode, i am looking at you), but it certainly works correctly in the vast majority of cases. The bug/task/backlog/etc tracking is the real center of TFS for me. And that side of things is amazingly flexible and configurable and works just fine.

    • Charles Chen says:

      Brad,

      I haven’t worked with TFS so I can’t give a definitive opinion from my perspective, but I’ve used SVN with Trac and just recently tested Mercurial with Redmine. Redmine, in particular, is really pretty slick when it comes to defect tracking and general SCM type functionality. Check it out if you’re interested. There’s a well-implemented all-in-one installer that’ll have you up and running in 10 minutes for purposes of testing. I’m strongly leaning towards adopting it for my next project.

      I’ve used Mercurial extensively over the last 6 months on a distributed project and found it generally a pleasure to work with compared to VSS and more suited to how I like to work when compared to SVN. I think some times, the folks that primarily work in the Microsoft solutions stack need to step outside of the box once in a while and see that there’s really a wide range of competitive options out there (open source and proprietary).

      VSS just left such a bad taste in my mouth (stopped using it since 2006) that I’m frankly a little “scared” of making an investment in TFS.

  2. Yes, it really is that bad.

    I “grew up” using Visual SourceSafe, and then TFS, and having switched to Mercurial two years ago (and as an occasional Git user) I cannot imagine a scenario under which returning to a centralised VCS would make sense. Every now and then something comes along that is simply better than what was there before – DVCS is one of those times.

  3. Yup, it sucks. TFS is a great example of a product with a major identity crisis–it does lots of things, none of them particularly well. And no one wants to integrate with it (think workflow or tooling), because the TFS licensing model sucks.