What Source Control tool do you use? And more on TFS Vs. Open Source tools

My blog has moved. You can view this post at the following address: http://www.osherove.com/blog/2007/4/29/what-source-control-tool-do-you-use-and-more-on-tfs-vs-open.html
Published Sunday, April 29, 2007 12:26 PM by RoyOsherove

Comments

Sunday, April 29, 2007 12:48 PM by Rachit

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

Very well said Roy! I agreed with you on most of the points.

Sunday, April 29, 2007 4:56 PM by Ayende Rahien

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

@Stephan,

The way I understand history, Excel and Word took the market by storm because their competitors were stupid.

Lotus 123 spent a lot of time re-writing their code, and the Word competitors didn't have a Windows version until very late in the game.

Also, can you think about the killer "embed excel in word" feature for TFS?

Monday, April 30, 2007 12:20 PM by Ryan Ternier

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

My bosses loved the open source source/control and bug tracking software because everything was displayed in "Table/Spreadsheet" views.

They're all old ENgineers. The developers were cryinging for TFS for months while it was in beta, heck we were even throwing tantrums, and we finally got our way mwhaha.

However, once we got TFS a few of the managers and directors hated it because looking at the Work Items was too hard for them. Until we showed them the Export to Excel... then we had to teach them... ignore that... then we had to write their queries for them.

But, once all that was done, they loved TFS. THere are many featuers of TFS that we can now not live wihout. The main one is the ability to check in code, and have it linked to bugs in the same system.

When MS Excel first came out, it sucked compared to Lotus 123. MS has always used the Speed to Market Strategy for new products. THey got Excel out, and then they improved on it. Eventually, it was better than Lotus 123.

Tuesday, May 1, 2007 11:03 PM by lb

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

suprised to see subversion poll so well. i thought of it more as an 'up and comer' than a 'most popular' winner.

Thursday, May 3, 2007 12:15 AM by RandomGuy

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

That's because subversion just works.  The thing I don't like with TFS is that I cant use it with my old VS 2003 projects.

Thursday, May 3, 2007 4:28 AM by Damien Guard

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

The thing putting me off TFS is the extortionately high pricing.

Team Edition for Software Developers - new installation... $5,469 for first year, $2,229 for subsequent.

Visual Studio Pro Edition is a $799 one-off.

Sure Subversion, AnkhSVN, Trac, NUnit etc. aren't well integrated but over a 3 year period you're paying nearly $10,000 PER DEVELOPER for integration.

Sure there are other benefits for being with the MSDN subscription it comes bundled with but not enough to justify $50,000 over the next 3 years for a small 5-man team.

[)amien

Thursday, May 3, 2007 7:13 AM by Antao

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

At our company, we have a full open source pipeline:

- Subversion

- TortoiseSVN

- AnkhSVN

- NAnt

- NDoc

- MbUnit

- Doubler

- NCover

- CruiseControl.NET

- Trac

It took some time to make it all work but we don't regret it. When a bug is found, the fix comes out way faster than with commercial products.

I have nothing against Microsoft. I love .NET and Visual Studio. I just think that open source is ahead of them on other tools...

Wednesday, May 16, 2007 9:13 PM by Dave

# re: What Source Control tool do you use? And more on TFS Vs. Open Source tools

We are caught between a rock and a hard place. We love the idea of TFS, we use Ms products every where else and am sure that the learning curve and features would be all but spot on but the price is exorbitant and that basically excludes it as a solution. It is a shame but it does not fare well for our environment of 4 developers. Something like Subversion seems to cover all bases but the learning curve for our network guys to set it up and for us developers (who currently use an old version of SourceSafe) to get into seems quite steep from where we are standing. The old version of SourceSafe has many, many problems but between price and learning curve, we are unfortunately stuck where we are for the moment.