Version Control with TFS
In order to use Team Foundation Server (TFS) for version control with Enterprise Architect, all users must have either the TFS command line client (tf.exe) or Microsoft's Team Foundation Server MSSCCI installed on their local machine. Each intended user must also have an account that provides read/write access to a workspace on the server.
This topic covers configuring version control using the TFS command line client. To configure version control with the TFS MSSCCI client, please follow the instructions in the Version Control with SCC topic.
The following preliminary steps should be performed within TFS on each PC and for each user, before making any attempt to define a Version Control Configuration within Enterprise Architect that uses TFS.
When initializing the connection to TFS, Enterprise Architect issues the command tf get. If the Local Working Copy path specified in Enterprise Architect's version control configuration is mapped through a TFS workspace that also maps many other working folders to their corresponding Source Control folders, TFS can take a long time as it proceeds to update the files in all of those folders. Enterprise Architect might appear to freeze when it initializes the connection to TFS, whilst it waits for TFS to complete the tf_get command and hand back program control.
Therefore, each user must set up a separate workspace for use in version control in Enterprise Architect, containing a single local working folder on their own machine that is mapped to a Source Control folder on the server. This separate workspace can be in addition to any other workspaces that might already exist.
To see a video demonstration of setting up a TFS project for version control, go to http://www.sparxsystems.com.au/resources/demos/settinguptfs/TFS%20Project-Workspace%20Setup.htm.