Comments on: A brighter TFS future? http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/ Strong opinions, weakly held Thu, 23 May 2013 23:40:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Mercurial, Git, and Elephant’s Graveyard System « Claudio Lassala's Blog http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3708 Mercurial, Git, and Elephant’s Graveyard System « Claudio Lassala's Blog Thu, 11 Aug 2011 16:43:50 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3708 [...] TFS may have a brighter future ahead, but until that day comes, I’m sticking with Mercurial and/or Git. GA_googleAddAttr("AdOpt", [...] [...] TFS may have a brighter future ahead, but until that day comes, I’m sticking with Mercurial and/or Git. GA_googleAddAttr("AdOpt", [...]

]]> By: Alexander M. Batishchev http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3666 Alexander M. Batishchev Sun, 07 Aug 2011 18:31:00 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3666 Virtualization is the key to your last inquire. Virtualization is the key to your last inquire.

]]> By: Pete Weissbrod http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3663 Pete Weissbrod Fri, 05 Aug 2011 14:41:00 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3663  Coming from someone who has worked with both TFS and free/OSS alternatives I would need to find a compelling reason to use TFS over a stack such as git/teamcity because so far I have found powershell scripts much simpler and equally effective.  Coming from someone who has worked with both TFS and free/OSS alternatives I would need to find a compelling reason to use TFS over a stack such as git/teamcity because so far I have found powershell scripts much simpler and equally effective.

]]> By: Chris Bristol http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3662 Chris Bristol Fri, 05 Aug 2011 12:49:00 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3662 As cool as this sounds on the surface, I don't know that its enough to make me think the cost of TFS is worth it. For me, TFS's vertical integration makes it far too costly to consider as a viable CI solution. At my last job, we chose TFS for source control, and it eventually became a major limiting factor in what we could do. We wanted to go to .Net 4.0 and VS2010, but since we would have to do a fair amount of work to get that working with TFS2008 and the corresponding MSBuild, we decided it would be better to wait for TFS2010. Unfortunately, going to TFS2010 seemed to require moving to SQL Server 2008, and that meant testing all the other apps that were running on that SQL server, which happened to be the only production one that company had. So the cost of moving forward was huge. We were stuck because of our CI system. Compare that with our previous setup using SourceSafe, Nant, CruiseControl, and BugTracker. SourceSafe sucked, but it was at least self-contained. Nant is free and works great. It did require some customization work for .Net 4, but its reasonable. Its been a while since I used CruiseControl, but I remember liking it a lot. BugTracker was also free, and did most of what we needed to do with the exception of non-bug work item type management. Sure, it was four distinct apps, but each one could be changed out on a whim. We were free to move around as necessary. The only features TFS provided to us were non-bug work item tracking and work item integration with the build.  For me, TFS was definitely a no win, at least in that environment. Unless you are a company with enough resources to dedicate a server  (probably at least 2, SQL and application) to your CI system, I think you are better off sticking with tools that are dedicated to doing one job well. As cool as this sounds on the surface, I don’t know that its enough to make me think the cost of TFS is worth it. For me, TFS’s vertical integration makes it far too costly to consider as a viable CI solution. At my last job, we chose TFS for source control, and it eventually became a major limiting factor in what we could do. We wanted to go to .Net 4.0 and VS2010, but since we would have to do a fair amount of work to get that working with TFS2008 and the corresponding MSBuild, we decided it would be better to wait for TFS2010. Unfortunately, going to TFS2010 seemed to require moving to SQL Server 2008, and that meant testing all the other apps that were running on that SQL server, which happened to be the only production one that company had. So the cost of moving forward was huge. We were stuck because of our CI system.

Compare that with our previous setup using SourceSafe, Nant, CruiseControl, and BugTracker. SourceSafe sucked, but it was at least self-contained. Nant is free and works great. It did require some customization work for .Net 4, but its reasonable. Its been a while since I used CruiseControl, but I remember liking it a lot. BugTracker was also free, and did most of what we needed to do with the exception of non-bug work item type management. Sure, it was four distinct apps, but each one could be changed out on a whim. We were free to move around as necessary.

The only features TFS provided to us were non-bug work item tracking and work item integration with the build.  For me, TFS was definitely a no win, at least in that environment. Unless you are a company with enough resources to dedicate a server  (probably at least 2, SQL and application) to your CI system, I think you are better off sticking with tools that are dedicated to doing one job well.

]]> By: lennybacon http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3661 lennybacon Fri, 05 Aug 2011 08:31:00 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3661 - 2012  NUnit support - 2014 Mercurial as SCM Maybe we can really use TFS in 2015 :-P - 2012  NUnit support
- 2014 Mercurial as SCM

Maybe we can really use TFS in 2015 :-P

]]> By: Viceroy http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3657 Viceroy Fri, 05 Aug 2011 00:41:00 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3657 Good share,you article very great, very usefull for us…thank you http://www.easyate.com/ Good share,you article very great, very usefull for us…thank you http://www.easyate.com/

]]> By: Andrew http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3655 Andrew Thu, 04 Aug 2011 21:53:00 +0000 http://lostechies.com/jimmybogard/2011/08/04/a-brighter-tfs-future/#comment-3655 "We're working on it."  Fantastic.   I mean, I feel bad for the little guy like Microsoft who don't have the resources to get their product to market with the features everyone wants...oh wait, nevermind. “We’re working on it.”  Fantastic.  

I mean, I feel bad for the little guy like Microsoft who don’t have the resources to get their product to market with the features everyone wants…oh wait, nevermind.

]]>