Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
TFS Workspaces
In order to use TFS to provide version control of the Packages in a model, you prepare a functional TFS workspace that can be accessed through an Enterprise Architect version control configuration within that model. You use the TFS workspace to map a local working folder on your PC to a Source Control Folder within a TFS project repository.
It is assumed that have TFS 2013 open and a TFS Team Project already exists for you to use in version controlling the Packages of your Enterprise Architect project. You can create the TFS workspace through MS Visual Studio.
TFS 2013 and later versions support the use of Local workspaces. However, Local workspaces do not support the application of checkout locks. For this reason, Sparx Systems strongly advises against the use of Local workspaces when version controlling your Enterprise Architect Package files. Using Local workspaces carries a high risk of merge conflicts when checking in, which would almost certainly result in loss of data or a corrupted model database.
Map a local folder to a TFS Source Control Folder
Step |
Action |
See also |
|---|---|---|
|
1 |
Connect to your TFS server. From the TFS main menu, choose View | Team Explorer. In the Team Explorer toolbar, click on the Connect to Team Projects button (fourth from left, with a power plug icon). The Team Explorer Connect page displays. |
|
|
2 |
Click on the link 'Select Team Projects...' The 'Connect to Team Foundation Server' dialog displays. |
|
|
3 |
Click on the appropriate Team Foundation Server, Team Project Collection and Team Project, then click on the Connect button. |
|
|
4 |
Click on the Home page of the Team Explorer, and then on the Source Control Explorer button. The Source Control Explorer view displays. |
|
|
5 |
In the Source Control Explorer, click on the drop-down arrow in the 'Workspace' field in the toolbar, then click on 'Workspaces' at the bottom of the list. The 'Manage Workspaces' dialog displays. |
|
|
6 |
Click on the . The 'Add Workspace' dialog displays. |
|
|
7 |
Click on the . A number of new fields display on the dialog. |
|
|
8 |
Type in an appropriate name for the new workspace and, if required, type in a comment. |
|
|
9 |
Set the 'Location' field to 'Server'. This setting is important. This setting is not available in TFS 2010 and earlier releases, where all workspaces are Server based. |
|
|
10 |
Click in the Source Control Folder column, then click on the to select a Source Control Folder. Select the Source Control folder (in the Team Project) to use for controlling Enterprise Architect Packages. |
|
|
11 |
Click on the in the Local Folder column and create a new local folder. This is the working copy folder into which Enterprise Architect exports the Package files. |
|
|
12 |
Click on the . The new workspace is created and saved. The 'Add Workspace' dialog closes. |
|
|
13 |
Click on the . The 'Manage Workspaces' dialog closes. |
Notes
- The local folder referenced in step 11 is the Working Copy Path that should be specified when defining an Enterprise Architect Version Control Configuration to use this TFS workspace
Learn more
