To prepare your TFS Project Collection for migration, you may want to remove (stale) old data to reduce the database size first. Most actions are already documented here. Queries that can aid in detecting where your space is allocated are also found in this recent support ticket. Delete old workspaces
In 2013.3 Microsoft did a number of massive changes to support Test Suites and Test Plans as work items. In 2013.4 only a few changes were made [http://blogs.msdn.com/b/bharry/archive/2014/10/16/visual-studio-and-tfs-2013-4-update-4-release-candidate.aspx] . There currently is no "upgrade my template"
There are times you hear nothing about a topic for over a year and then suddenly 2 clients and an MSDN forum post [http://social.msdn.microsoft.com/Forums/vstudio/en-US/df481a58-35be-4557-ba12-6c10f0a9933a/results-from-test-runs-on-web-in-tfs?forum=tfsreporting#38d11198-9341-4f9a-bc36-242125a89948] come up with the same request: Can we show the test results in Team
> Update: Project has been uploaded to GitHub [https://github.com/jessehouwing/tfstools]. One of the teams I work with recently had strange issues when they tried to merge their feature branches to the main branch. It turned out that one developer had accidentally misconfigured his workspace and was check-in
Update * Download the latest version here. [https://marketplace.visualstudio.com/items?itemName=jessehouwing.azure-boards-teams-tool] Some time ago I blogged about the few lines of code required to convert a TFS Group to a Team [https://jessehouwing.net/vsts-tfs-convert-security-group-to-team]. It's now available as part of the latest version of
Update I've since uploaded a patch to the TfsTeam quick response sample to also include functionality to convert a Group to a Team. [https://jessehouwing.net/vsts-tfs-team-tools-convert-security-group-to-team] With TFS 2010 it was already a common practice to create security groups as subgroups of the Contributors group to define
| | | Types inheriting from UITypeEditor | Recently I was asked to extend a Build Template for Team Build. There were a few fancy things which were required for this template, including picking files and folders in Source Control, selecting Work Items etc. I looked around the documentation on msdn.microsoft.com, but
Update: I've posted a consolidated post for all versions of Visual Studio and Team Foundation Server here. [https://jessehouwing.net/vsts-tfs-connect-any-visual-studio-version] Not all of us are so lucky that we can work with the latest bits at all time. Especially the folks that are in the Microsoft BI