Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Create a TFS Environment
Before Enterprise Architect can be used with TFS, the appropriate software must be installed by a TFS administrator. Ask your system administrator to obtain and install the TFS server and client applications.
The following topics describe some basic tasks that must be completed in order to create a TFS environment that can be used by Enterprise Architect
Topics
Topic |
Detail |
See also |
|---|---|---|
Obtain and install TFS |
Enterprise Architect uses the TFS command line client to integrate TFS version control. It is assumed that the TFS command line client is installed as part of your Visual Studio installation.
|
|
Choose a TFS project |
It is good practice to create folders in your PC's file system for organizing your files and documents. Similarly, it is good practice to create a new TFS project, or least a new Source Control Folder within a project, for each new Enterprise Architect project. If you have a single Enterprise Architect project, that contains many different models, (for example, a DBMS hosted project with multiple model root nodes), you might choose to create a new TFS project for each separate model. Please consult your TFS documentation.
|
|
Create a TFS workspace |
The TFS workspace is used to map a local working folder on your PC, to a Source Control Folder within a TFS project. A single TFS workspace can map many different local folders - each one to a separate Source Control Folder. You can gain performance benefits for some of Enterprise Architects version control operations if you keep your version controlled package files in a folder that is separate from other artefacts, such as source code files. This can be achieved either by creating a separate work space to use just for your package files, or by creating and mapping a separate folder for package files within an existing workspace.
|
|
Configure exclusive check-outs. |
The XMI file format used for version control of Enterprise Architect's packages can not be merged like ordinary text files. Therefore, Enterprise Architect must enforce serialized editing of its version controlled packages. As a consequence, it is important that TFS is configured to use 'exclusive checkouts' for XML files.
|
Notes
| • | TFS can also be used with an SCC client. The MS TFS-SCC client is available for download from Microsoft's web site |
| • | Visual Studio Integration (MDG Integration for Visual Studio 2005 or 2008) enhances TFS support by providing access to, for example, work items and bugs within both Enterprise Architect and the MDG Integration product |
Learn more
