Before using Enterprise Architect's version control facility, your version control product must be installed on each machine where it is intended to be used. Version Control products supported by Enterprise Architect include MS Team Foundation Server, Subversion, CVS or any other version control product that provides an MS SCC-compliant interface.
Note: Although Enterprise Architect directly supports TFS through its command line interface, we recommend the use of Microsoft's TFS-SCC client instead.
Typically there should be:
| · | A server component that manages a version control repository |
| · | Client components on the workstations that Enterprise Architect uses to communicate with the server. |
A version control client must be installed on every machine where you run Enterprise Architect and want to access your version control system. Once the version control software has been installed and configured, you must define a Version Control Configuration within Enterprise Architect, to use your installed version control product.
Note: If you are using the Corporate version of Enterprise Architect with security enabled, you must also set up permissions to configure and use version control. See List of Available Permissions for further information.
Version control can be assigned to individual packages, view nodes or root nodes in Enterprise Architect. Each package can only be linked to one Version Control Configuration at a time, although it is possible to connect multiple control configurations for each model. You can use the Version Control Configurations dialog to set up a connection to your version control application.
To set the Version Control Configuration, select the Project | Version Control | Version Control Settings menu option.
Go to the Version Control Settings Dialog topic.
See Also