Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have worked with JIRA / Subversion and now with TFS 2010, and I think JIRA / Subversion are much better tools. </p> <p>I like the idea of having source control, workitem control, build control, test control in one integrated package, but somehow TFS is just a <a href="http://www.derekhammer.com/2011/09/11/tfs-is-destroying-your-development-capacity.html" rel="nofollow noreferrer">below average implementation</a> of everything (Except Gated Checkin because that is cool).</p> <p>TFS version control uses binding just like VSS, so doing multiple checkouts of the same requires extra effort. The ability to Suspend/Resume work using TFS shelveset, is the official workaround for being able to do concurrent work.</p> <p>TFS sometimes goes haywire with its SQL table locks, so it has be restarted. Also the SQL indexes randomly gets broken, so suddenly showing folder history takes minutes. TFS in VS2010 needs to be online all the time to do any source editing, though this has been fixed in VS2012. But the VS2012/VS2013 GUI is so tightly integrated with TFS, so if the TFS-server has issues, then everything becomes sluggish in VS. This is really visible with the new VS2015 CodeLens, where all TFS WorkItem Lookup should be disabled, or else VS2015 will get stuck more often than usual.</p> <p>Visual Studio will one or two times during a work week fail to get latest source (sometimes silently). If you attempt to get latest again, then it will say you already have latest. When you perform a build, then it will ofcourse fail. The workaround is to perform a get specific version with forced overwrite.</p> <p>To create a wiki for documentation, then one have SharePoint, and version 2010 is a really crappy wiki tool.</p> <p>For some really strange reason Microsoft System Center (really expensive) is completely detached from the TFS solution, and lingers around like an old lady. Making it super difficult to synchronize incidents with TFS-workitems, and get TFS-builds deployed using System Center. VS2013 Update 4 now includes the almost free InCycles Release Management, that should make the continuous integration work better (IIS applications can use <a href="http://www.iis.net/downloads/microsoft/web-deploy" rel="nofollow noreferrer">Web Deploy</a>). </p> <p>If you work with advanced stuff like release-branching, then you will be surprised how difficult it is to generate a release notes document (read requires unsupported 3rd party tools). There is no automatic association of <a href="http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2047315-merge-by-workitem" rel="nofollow noreferrer">Work Items when merging</a> to release-branch. And if you suddenly want to release a new build, then no help around for creating a release-report that lists the changes/workitems that has been included since last released build.</p> <p>The integration of JIRA/Subversion in Visual Studio (VisualSVN) is so much better (ankhsvn is an alternative opensource version of VisualSVN). Still don't understand why Tfs-annotate cannot jump to next previous version like Svn-blame can.</p> <p>I have no idea about the difficulty of setting up TFS 2010/2012, but JIRA / Subversion / CruiseControl.NET was very easy and cheap (Guess one would now use Git and <a href="https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin" rel="nofollow noreferrer">Jenkins</a> that also supports <a href="https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Plugin" rel="nofollow noreferrer">Gated Checkin</a>).</p> <p>VS2012 also includes a redesign of the entire user interface, which includes a new "improved" TFS Team Explorer that is really a pain to work with as a developer (Compared to VS2010). Microsoft has declared that <a href="http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2654486-window" rel="nofollow noreferrer">Team Explorer has been fixed in VS2013</a>, but it is not true. It is mouse-click hell to perform checkin and associate tfs-workitems.</p> <p>Visual Studio 2012 now includes a virtual kanban board, but I would be surprised that this feature is not added to JIRA. </p> <p>Became very suprised when the Visual Studio Team announced that they will implement GIT support in Visual Studio 2012. Guess it is easier than trying to rewrite TFS into a distributed version control system. Hope the new GIT integration will come up to the standards of VisaulSVN. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload