Archives for November 2012

Visual Studio 2012 Update 1

Microsoft changed the release cycle of Visual Studio and Team Foundation server, from now on there are going to be quarterly releases of both products. The first update (Update 1) is here and this is what it contains:

  • Extend TFS server side path limits from 260 characters to 400 characters
  • Usability improvements for Version Control
    • Associate multiple bugs with a checking at once in the Add by ID field (i.e. comma separated)
    • Toolbar button to show/hide deleted items in the source control explorer
    • Copy the name of a changeset/shelveset from the Changeset/Shelveset Details page
    • Find a Shelveset by name from the Find Shelvesets page
    • Include/exclude all items except those that are selected
    • Know if my detected changes are adds or deletes before clicking the link
    • Navigate to an item in source control explorer from pending changes page
    • Undo changes to a file from the editor context menu
  • Kanban support in TFS Web Access
  • TFS web access usability improvements
    • Drag and drop queries and query folders
    • Drag/drop between User Stories and People in the Taskboard
    • Drag a task to a person to assign it in the Taskboard
    • Expand and Collapse the left navigation pane
    • Remember the state of the splitters
    • Animate Taskboard tiles on drop
    • Next/Previous arrows on WIT form
    • Updated navigation styling
    • Links and Attachments in WIT form shows counts
  • Sharepoint testing improvements
    • Load testing support for SharePoint
    • Unit test emulator for SharePoint
    • Coded UI test support for SharePoint
    • Intellitrace collection plan for SharePoint
  • Manual testing improvements
    • Editing of test cases from inside the test runner
    • Code coverage support for manual testing of web apps
    • Hierarchical query support
    • Pause manual testing session and later resume a test case
    • Deep copy of a test plan to better support release management
    • Publish test results to TFS from command-line
  • Coded UI testing improvements
    • Cross browser testing for coded UI testing (IE, Chrome, Firefox, …)
    • Usability improvements for Coded UI tests
  • SCVMM 2012 SP1 support with Lab Management for Windows 2012 hosts
  • VSUpdate support for Microsoft Test Manager for automatic update notification
  • Unit testing improvements
    • Windows Store C++ unit testing enhancements
    • Windows Store Unit Test library enhancements
    • Traits support for all adapters
    • Unit Test Grouping and Filtering in Test Explorer Window
  • Easier installation of unit test adapters on TFS build machines using Nuget
  • Code Map – Incremental discovery and visualization of your application architecture and dependencies
  • IntelliTrace Integration with System Center
  • Integrate Blend Windows Phone Tooling
  • Multiscale image support for manifest content
  • JavaScript Memory Profiling
  • Mixed Managed/Native Debugging Support for Store Apps
  • ARM Native Dump Debugging Support
  • Enable XP targeting with C++

Read more at the Visual Studio + ALM Team blog

My personal favorites are the Kanban support and the new drag and drop features in TFS Web Access.

Download the Visual Studio update here and the Team Foundation Server update here.

Read Damians blog for a detailed instruction for the TFS upgrade.

There is also an update for Team Foundation Power Tools to match the service update, download it here

In Visual Studio 2012 Update 2

In Visual Studio 2012 Update 2 we will among other things se test case management and manual testing from within a browser!

Team Foundation Service

If you want to see what probably be included in upcoming Team Foundation Server releases you should take a look at Team Foundation Service, the cloud based version of TFS. Team Foundation Service has a release cycle of three week. Read more in their blog.




Migrating Scrum for Team System 3.x to MS Scrum 2.0

A lot of you have probably used the Scrum for Team System process template from Conchango in previous versions of Team Foundation Server (pre 2012). Scrum for Team System is now an open source project on Codeplex and I haven’t seen any plans to a TFS 2012 versions. For those of you wanting to use the new TFS 2012 features I have two recommendations:

  1. The easiest way is to create a new TFS project and start using it
  2. If you want to upgrade an existing project read my blog below.

Download Work Item type definitions

  1. Download the process template for MS Scrum 2.0 and Scrum for Team System 3.0x with the Process Template Manager for example to C:MyDownloadedTemplates.  If you have modified the Scrum for Team System with fields of your own you should download those instead.

Change Work Items

  1. Identify and copy fields that you use that differ from Scrum for Team System to the MS Scrum Work Item definitions and identify the state changes between the templates. Some of them also include name changes of the Work Item type definition. If you have added fields of your own you should also include them.
Conchango WI MS Scrum WI Field mapping States mapping
Product backlog item Product backlog Item
  •   Business value (Scrum) – Business Value
  •   Storypoints – Effort



  •   In progress – Comitted
  •   Not Started – New
  •   Deleted- Removed
  •   Descoped-Removed
  •   Broken –  Removed
  •   Depricated – Removed
Sprint backlog task Task
  • Task Priority (Scrum) – Backlog Priority
  • Work Remaining (Scrum) Remaining Work
  •   Task Priority (Scrum) – Backlog Priority
  •   Work Remaining (Scrum) Remaining Work
  •   Not Started – To Do
  •   Deleted – Removed
  •   Descoped – Removed
Bug Bug
  •   Active – New
  •   Ready For Test – Done
  •   Closed – Done
  •   Deleted – Removed
  •   Ignored – Removed
Acceptance test Test Case
  •   Not Implemented – Design
  •   Deleted – Closed
  •   Ready for Test -Ready
  •   Passed – Ready



Here is what the PBI modification may look like

Here is what the Task modification may look like. Note that I have changed the name of the MS Scrum Task to Sprint Backlog Task so that is will overwrite the existing WI definition, it will be renamed later.


Upload Work Item Type definitions

Upload the modified WIs from the MS Scrum template to the project that is to be modified with witadmin.exe.

1. Start a Visual Studio command prompt and run the command below

CD C:MyDownloadedTemplatesMicrosoft Visual Studio Scrum 2.0WorkItem TrackingTypeDefinitions

2. Upload the product backlog Item WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”ProductBacklogItem.xml”

3. Upload the Task WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”Task.xml”

4. Change name of the WI from Sprint Backlog Task to Task

witadmin renamewitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject”  /n:”Sprint Backlog Task” /new:”Task”

5. Upload the Bug WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”Bug.xml”

6. Upload the TestCase WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”TestCase.xml”

7. Change name of the WI from Acceptance Test to Test Case

witadmin renamewitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject”  /n:”Acceptance Test” /new:”Test Case”

8. Upload the Impediment WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”Impediment.xml”

9. Upload the Shared step WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”SharedStep.xml”

Copy fields using excel

Use Excel to copy fields between the old and the new fields that differs. Also use Excel to change the stare model.

Remove WIs that are not used.

The following WIs are not used in the MS Scrum template, remove them.

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Sprint Retrospective”

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Release”

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Sprint”

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Team Sprint”


Work Item Queries

1. Create a new WIq folder called Old and move all old Queries there

2. Copy WIQs from a project  Created with MS Scrum with copy-paste

3. Modify queries under the Current Sprint folder to match your sprints


Change sharepoint

You may not be able to access the SharePoint site because old web parts might be missing, to fix this follow these steps.

  1. Go to Site settings, http://MyTFSserver/sites/MyCollection/MyProject/_layouts/settings.aspx
  2. Activate sites features Scrum Dashboards with reporting and Team Collaboration Lists
  3. Go to http://MyTFSserver/sites/MyCollection/MyProject/Dashboards/Forms/AllItems.aspx
  4. Select ”Open with  Windows Explorer”
  5. Copy Release.aspx and overwrite Default.aspx
  6. Go to Site settings, choose ”Title, Description and Icon”
  7. Change the Icon URLto /_layouts/Microsoft.TeamFoundation/images/tfstitlegraphic.gif
  8. Click update the user interface



Add new reports

  1. Remove the old reports
  2. If you haven’t installed Team Foundation Power Tools, install it.
  3. Run tfpt addprojectreports to add the new reports

tfpt addprojectreports /collection:http://MYTFSSERVER:8080/tfs/MyCollection /teamproject:”MyProject” /processtemplate:”Microsoft Visual Studio Scrum 2.0″ /force


Add TFS 2012 functionality

1. Start TFS Web access for the project

2. Click Backlog

3. Click Configure

4. Click Verify

5. Click Configure

6. Click Close


You now have I migrated project with a new process template. Next step is to set dates to your Iterations and add members to your team!