3

We are about to roll out a project management system and we came across TFS. It seems pretty powerful as it can integrate version control system and project management tools into one server. But we are not a visual studio shop. Our development is done with Java/Php/Obj-C. Is TFS still useable without VS?

pnuts
  • 58,317
  • 11
  • 87
  • 139
erotsppa
  • 14,248
  • 33
  • 123
  • 181

3 Answers3

3

The key difference between TFS and the rest is the highly integrated nature of Source Control with Worth Item tracking and the fact that you have a data warehouse on top of both.

In terms of raw source control features, TFS and Subversion compare well. Obvioulsy, TFS has the benefit of talking to SQL Server 2005, meaning that any SQL tools and knowledge can be used to backup the database etc, off the top of my head - Subversion lacks the shelving, the caching proxy and and lightwieght labelling features but does have a better offline story than TFS V1.

TFS, Subversion and things like Vault are great, modern, Source Control systems. You'll notice I left VSS out of that list :-). While the Source Control features of TFS are very good - it does much, much more stuff than version control...

You can also take a look at some other studies have been carried out. But then again, just because other people have decided to adopt the product doesn't mean that you have to. There is plenty of competition in the developer tools market for you to get the tools you need at a price that you can afford.

In terms of convincing your management, then an explaination of the integration between work item tracking and source control along with a cost comparison of buying the equivalent (not integrated) products for your organisation should do the trick.

code master
  • 2,026
  • 5
  • 30
  • 49
2

I wouldn't wish TFS on my worst enemy. I've only ever used it for source control and have no experience with its other facilities, but it has caused me immense grief. TFS source control facilities are cumbersome, complicated, incomplete, error prone, failure prone and generally difficult to use. I only use it because I'm forced to at work. Even if project management tools were totally awesome (which I gather they're not) I wouldn't want to use them because of the pain TFS source control regularly causes me.

There are plenty of more or less reasonable analyses of this tool on the web (in addition to all the hate filled diatribes). Here are a few from nearby:

Should we migrate from svn to Team Foundation Server 2010?

Experience with SVN vs. Team Foundation Server?

TFS vs SVN

Community
  • 1
  • 1
Mr. Putty
  • 2,276
  • 1
  • 20
  • 20
  • That's a pretty biased comment. I've been using TFS since version 2008 and it never caused data (source code) to be lost. It might be difficult to admin sometimes (like setting permissions on multiple servers - tfs, report server, sharepoint, etc), but that's the price you pay for using a product that can be used by small and large teams alike. – Padu Merloti Aug 29 '11 at 18:30
  • 2
    My opinion is indeed biased. It is biased by years of experience with TFS. Just because a VCS has not lost any source code doesn't make me want to use it. Is that really the bar you'd use to measure systems for a commitment as large as choosing a project management/VCS? Because I do recognize my bias, I did include some links to less biased source. – Mr. Putty Sep 21 '11 at 14:55
0

With the languages you mention, you might look into using Jazz. http://www.jazz.net

James Branigan
  • 1,164
  • 7
  • 9