| Prev | Next |
TFS Settings
When you are setting up your Version Control configurations on the 'Version Control Settings' dialog, and you set the configuration type to 'TFS', the dialog presents a set of fields specific to TFS-based configurations. You can then define details such as:
- The working copy folder to be used with the configuration
- The user name and password to log in to the TFS server
- The path to the TFS command line client
Access
|
Ribbon |
Configure > Version Control > Project-VC: Type: TFS |
|
Context Menu |
Right-click on Package > Package Control > Version Control Settings: Type: TFS |
Settings
Option |
Action |
See also |
|---|---|---|
|
Working Copy Path |
Displays the full path of the folder that contains the local (working) copies of the XMI Package files. This field is read-only; its value can only be set through use of the associated . |
|
|
Select Path |
Click on this button to choose the Working Copy Path. The file browser dialog opens, through which you navigate through the file system to the appropriate folder. |
|
|
Server Name |
Displays the name of the TFS Server that is associated with the working copy folder specified in the 'Working Copy Path' field. This field is read-only; Enterprise Architect retrieves the value it displays by querying the TFS client. |
|
|
Workspace Name |
Displays the name of the TFS Workspace that is associated with the working copy folder specified in the 'Working Copy Path' field. This field is read-only; Enterprise Architect retrieves the value it displays by querying the TFS client. |
|
|
User Name |
Type in the user name with which to log into the TFS Server. |
|
|
Password |
Type in the password with which to log into the TFS Server. |
|
|
Display Name |
TFS 2013 and later releases use a Display Name to report on who owns a checkout lock on a file. TFS 2010 uses AccountID when reporting lock owners and so does not require a Display Name. If using TFS 2013, type in your TFS Display Name as shown in the User column of the Visual Studio Source Control Explorer when you checkout a file. |
|
|
Checkout Locks Required |
This checkbox defaults to selected. TFS 2013 supports the use of Local workspaces, but these do not support checkout locks. If you want to use TFS Local workspaces (not recommended), you must deselect this checkbox. Otherwise, leave the checkbox selected. It is recommended that all workspaces used for Version Controlling Enterprise Architect Package files are set as 'Server' workspaces. |
|
|
TFS Exe Path |
Displays the full path of the TFS command line client executable file. This field is read-only; its value can only be set through use of the associated . |
|
|
Select Path |
Click on this button to specify the path to the TFS command line client. The file browser dialog opens, through which you navigate through the file system to the appropriate folder. |
|
|
VC Time-Out Value |
Type in the number of seconds that Enterprise Architect should wait for a TFS command to complete; if a command does not complete within this allowed time, the system displays a Time-out error message, detailing the command that failed to complete. This single time-out value is applied to all Version Control configurations (of types SVN, TFS and CVS) that the user accesses from this workstation. |
Notes
- If you automatically log in to TFS through a path external to Enterprise Architect (for example, through MS Integrated Security), you can leave the 'User Name' and 'Password' fields blank
- If the 'Password' field is blank, Enterprise Architect retrieves your Windows username and uses that value when determining whether a Package file is checked out to you or to another user
- TFS Version Control can also be accessed using the TFS MSSCCI client; to make use of the TFS MSSCCI client, please define an SCC based Version Control configuration
- You define the TFS-specific details as part of the broader process of setting up a Version Control configuration on the 'Version Control Settings' dialog