Renaming a Project in TFS

December 21st, 2007

I’ve recently decided to try out Microsoft’s latest incarnation of Team Foundation Server; a document and code versioning, as well as defect tracking system for developers.

Since TFS manages source code, as well as documents, it is an extremely convenient repository of data for your projects; yet – by putting all your eggs in the one basket, you may be unpleasantly surprised when you decide to rename your project. In Team Foundation Server 2005, this ‘feature’ was absent, if you were hoping to find it in 2008 – stop looking, there are too many DB references to update. We can only hope that Microsoft will bring about a tool to do this as part of a service pack.

  • anonymous
    TFS has build problems...managing builds suck in TFS.

    One word: Look up Subversion.
  • anonymous
    That is three words, and if all you want is a free source code repository, you are correct. TFS is a "System" of Software Development Life Cycle tools. Including Requirements Gathering, Work Item Tracking, Defect Tracking, SDLC Reporting, and it happens to also include a source repository not to mention the Test Suite including Unit Automation, Stress and Load testing as well as manual test results recording.

    As for the OP, if all you got out of your TFS exploration was the fact that you can't rename a project, I strongly suggest you take another look. I use TFS for my personal dev, and have set it up at my current employeer as well as three other companies.

    Enjoy!
  • anonymous
    That's interesting: Does Subversion support builds at all? I like Subversion but you really can't compare it to TFS. Besides, I think managing builds in TFS is really nice (at least in TFS 2008) ;-)
  • This isn't so much about whether subversion supports builds or not, it concentrates on doing one thing, and one thing only. The premise on which all apps for *nix are made.

    Mind you, not to say that TFS is bad, as for the time that I used it, I very much enjoyed working with it.

    What the post was about, was just indicating one of the deficiencies or expectations within TFS that wasn't met.
blog comments powered by Disqus