This project is read-only.

Release Notes

Migration Sync Toolkit v1.1 (Prerelease)

The purpose of this release is to fix many of the issues in the v1.0 release of the toolkit. The new features contained in this release are small in number, and have been added primarily to support the TFS to TFS tool functionality.

Prerequisites

  • It is recommended that the latest client and server bits are used wherever possible. Also, the TFC version used should be greater than or equal to the TFS version (i.e. for a 2008 server, use 2008 or 2008 SP1 client)
  • TFS 2005 Service Pack 1 is the minimum version for both the server and the client machines
  • A SQL Server 2005 database must be deployed

Improvements in this Release

  • Indices have been added to improve the migration performance.
  • Compatibility improvements have been made to better support migrations between different TFS server versions.
  • WSS samples have been fixed.
  • If the account used to run a migration is not in service account group, a warning will be given.
  • Numerous improvements have been made for migration scenarios involving renames.
  • Wait time between session status updates run from migrationconsole.exe is configurable via the "wait" parameter. The default is 60 seconds.
  • Analysis now handles more than 512 consecutive changesets.
  • Undelete of multiple deleted items is now supported.
  • A new configuration setting has been added to handle the migration of branched items for which the source branch is not being migrated. The new boolean setting name is "ChangeToAddOnBranchSourceNotFound", and the resulting action is that if the source of a branched item is not in scope for the migration, the item will show an "add" change type in the TFS history (as opposed to a "branch" change type). In the case of a merge with the source item not being mapped, the change type will be "edit" in place of "merge". The default behavior for this setting is to abort the migration session (setting value is false).

Known Issues/Limitations

  • Limitations from the v1.0 release still apply to this release (see below).
  • Migration of destroyed items/versions is not supported. If an item is completely destroyed, there won't be a problem with migration (nothing exists to migrate), but if the /keephistory option was used when an item was destroyed an exception will be thrown when the toolkit tries to download the file contents.
  • If an item is renamed out of the mapped path, the migration toolkit will not delete the item. This can result in failures if items are added/renamed into the path in the future. A workaround may be to map at a higher path that includes the target of the rename.
  • In the case of a Merge,Delete, the merge bit will be lost.

Migration Sync Toolkit v1.0

This is the first full version of the TFS Migration and Synchronization Toolkit. Included in this release are the components to migrate and synchronize VC and WIT data, metadata, and links, two reference implementations for syncing data between TFS and WSS, and a sample host process to run migration sessions. This version has undergone a much more complete series of functional testing, and is production quality.

Prerequisites

In order to use the toolkit and run the samples, the following criteria must be met:
  • Service Pack 1 for TFS must be installed on the server and the client machines
  • A SQL Server 2005 database must be deployed
    • This must be a separate database from the SQL Server instance used by TFS
    • The express edition can be downloaded for free here: SQL Server 2005 Express

Known Limitations

  • Labels are not detected in the analysis phase. This is by design. However, if a label operation is added to the migration queue during the analysis phase, it will be migrated.
  • WIT systems that do not support file attachments and links must still implement the IMigrationFileAttachment and IMigrationLinkOperation interfaces. Returning an empty collection is a possible work around, but TFS must be the master system (to avoid overwriting the attachments with an empty collection).
  • The Toolkit cannot migrate work items with SERVERDEFAULT from=”clock”/> rules. All types containing such rules must disable the rules for the account that will run the migration tool. An example of this change is shown below.
    • <SERVERDEFAULT from=”clock” not=”DOMAIN\jsmith”/>
  • The TextReport adaptor must be given a file with a path under the <File> node. Failure to supply a path will result in an error. To place the text report file in the working directory, the following text can be used:
    • <File>.\Report.txt</File>

Cannot resolve release macro, invalid id.

Please note that this is a prerelease version of the Migration and Synchronization Toolkit. Several features are not complete and as testing has not completed, the code has the potential to contain bugs and overwrite data stored in TFS. Please be careful to use this only in a testing environment and not on live production data.

Prerequisites

In order to use the toolkit and run the samples, the following criteria must be met:
  • Service Pack 1 for TFS must be installed on the server and the client machines
  • A SQL Server 2005 database must be deployed
    • This must be a separate database from the SQL Server instance used by TFS
    • The express edition can be downloaded for free here: SQL Server 2005 Express

Known Limitations

  • The WSS to TFS provider for WIT is not fully operational at this time. It should be used only as an example of how to approach writing a WIT provider.
  • Labels are not detected in the analysis phase. This is by design. However, if a label operation is added to the migration queue during the analysis phase, it will be migrated.
  • WIT systems that do not support file attachments and links must still implement the IMigrationFileAttachment and IMigrationLinkOperation interfaces. Returning an empty collection is a possible work around, but TFS must be the master system (to avoid overwriting the attachments with and empty collection).
  • The toolkit cannot migrate work items with SERVERDEFAULT from=”clock”/> rules. All types containing such rules must disable the rules for the account that will run the migration tool. An example of this change is shown below.
    • <SERVERDEFAULT from=”clock” not=”DOMAIN\jsmith”/>
  • The WitSync tool for testing WIT migration session must have a <Provider> node in the configuration file to execute properly. A sample node is included in the SampleWITConfig.xml file, but it requires that the Wss2TfsWit.dll is located in the MigrationConsole\bin\Debug directory with the WitSync.exe.
  • The /c:configfile.xml option for the WitSync tool does not work correctly. The workarounds are to name the config file "witconfig.xml" and place it in the same directory as WitSync.exe, or specify the file location in the "WITSYNC_CONFIG" environment variable.

Last edited Sep 16, 2008 at 8:14 PM by mmitrik, version 12

Comments

No comments yet.