Anith Gopal

Grant C. recently sent us this question: “ I saw mention in the log of a TfsMigrationTool.ReflectedWorkItemId field but couldn’t find any docs / discussion about it.  I added it to my target WIT and also added my own TfsMigrationTool.SourceProject field as you can see in the config, but I’m curious if there are any other TfsMigrationTool.x fields the tool automatically sets. ” Great question, which allows us to introduce an originally internal Pioneer dog fooding feature, but one that could be invaluable to users of the TFS Integration Platform in WIT migration and/or synchronization scenarios.

Late last year we started the Visual Studio 2010 Architecture Guidance project … probably the worst time as December is a very inactive month with everyone enjoying a well deserved break and January  being a very active month to re-start initiatives, thus having little time and bandwidth for these kind of projects. Nevertheless the team has ensured that the guidance project is picking up momentum and recently released a DRAFT of the core scenarios to the Rangers for comment and are hard at work on a BETA release for the core scenarios and a DRAFT release for the extensibility and Hands-on-lab (HOL) scenarios.

Two kind-of questions recently bubbled up on the radar: Should we manually copy (migrate) files from source to target, to reduce the work that the TFS Integration Platform needs to do? In other words, does it help to be pro-active? No, because this manual action will introduce a “VC content conflict type” for every file that was migrated.

Thanks to everyone who attended our TFS Migration Tools TR9 re-run and a special thanks to Bill Essary and his team for supporting the VSTS Rangers “again”.  Apart from me running on my server after re-installing my laptop with Win7 over the weekend and an “important update install and imminent restart” warning message on the server just before the start of the session, the re-run went fairly well.

We have been working to create a home for the VSTS Rangers and their projects, to recognize the phenomenal contributions made by Team System experts and to better understand the interest in our VSTS Rangers projects. Thanks to Sharon , we now have our very own site Please check out http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx which is the first iteration of our new VSTS Rangers home page and associated Solutions and Projects page