|
Conversion Process
|
Top Previous Next |
| 1. | Origin project scanning - CS-Converter scans all file revisions in the origin project and sorts them according to check-in changesets. All files checked-in together using one command, are identified as a single changeset.
|
| 2. | Username mapping - When CS-Converter detects any origin username that doesn't have a matching TFS username, it prompts the mapping of origin usernames to TFS usernames.
|
| 3. | Conversions - CS-Converter loops through the origin changesets and for each such changeset, performs an identical check-in command to TFS.
|
| 4. | Status calculations - CS-Converter loops through the files and verifies the conversion.
|
| · | Depending on the size of your project, number of branches you want to convert and the network protocol used, full project conversion may take several hours.
|
| · | No special preperaions are needed to be performed on the origin repository. However, please note that CS-Converter converts logically deleted (e.g. CVS 'dead' state) files, since you may need the files' earlier revisions in order to retrieve project releases. If you have a large file that is completely redundant, remove the file from the origin repository prior to selecting the project in CS-Converter.
|
| · | Users may continue working with the origin repository during conversion. CS-Converter detects new revisions added to the origin repository and suggests to convert these new revisions.
|