Friday, June 29, 2007

TFS Migration and Synchronization Toolkit 1.0 Released

CodePlexTFS Migration and Synchronization Toolkit

"The purpose of the TFS Migration and Synchronization Toolkit is to enable customers of Team Foundation Server (TFS) to build custom tools that enable migration and synchronization with other version control (VC) and work-item tracking (WIT) systems. Customers have asked us for this toolkit to help them integrate TFS into their existing development environments. Please give it a try and let us know what you think.

...

  • Bi-directional synchronization of data between TFS and another system allowing teams to transition over time
    • Enables integration of TFS with other VC and WIT systems (i.e. using TFS for VC but a proprietary system for bug tracking)

    ..."

    From the readme.txt;

    "This is the 1.0 version release of the Migration and Synchronization Toolkit.  Included in this release are the components to migrate and synchronize version control (VC) and work item tracking (WIT) data to TFS, components to synchronize links between changesets and work items, and two reference implementations.  The first reference implementation synchronizes WSS documents to TFS VC, and the second synchronizes WSS task lists to TFS work items.

    ..."

    Ed Hintz (MSFT) - TFS Migration and Synchronization Toolkit Released to the Wild

    "...

    If you download the toolkit, I encourage you to look at the reference implementation that migrates with SharePoint (WSS).  This implementaiton migrates documents between SharePoint and TFS version control as well as migrating SharePoint task lists with TFS work item tracking. ..."

    Interesting.

    I have a number of users who are comfortable in SharePoint but not yet with TFS (or any of the TFS access points). I think it would be pretty cool to be able to provide them a WSS list interface to selected TFS Work Items (and there's NO way I was ever going to copy and manually/human sync WSS <-> TFS... that way leads to madness and I'm sure would quickly be put aside. No a automated sync solution is the only viable choice...).

    Hum... Now just to find the time to dig into this...

    No comments: