In order to use SQL Navigator’s Team Foundation Server support, you need to have Team Foundation Server (TFS) installed on your network. Please review Microsoft's documentation for instructions on installing and configuring TFS.
Additional requirements are needed to work with TFS work items.
Team Coding includes two methods for interfacing directly with TFS: an internal client and an external client. Although they have identical TFS functionality in SQL Navigator, each client has its own unique advantages and disadvantages. See your TFS administrator before configuring it in SQL Navigator.
Internal TFS Client Uses Microsoft’s Web Services API to directly communicate with Team Foundation Server. |
Advantages: Improved speed (over the external client) No need to install additional software on the client machine Disadvantages: Does not include support for Check-in Policy items Certain administrative tasks, like deleting workspaces are not supported |
External TFS Client Uses Microsoft’s command-line Team Foundation client to communicate with Team Foundation Server. This command-line client is included with Microsoft Team Explorer, and should remain consistent throughout versions. |
Advantages: Expected compatibility with future versions of Team Foundation Server Supports all features of Team Foundation Server, including Check-in Policies Disadvantages: Much slower than the internal client since an instance of the external client is launched for each TFS command issued to the server Requires the installation of Microsoft Team Explorer |
Team Coding check-in includes the ability to link one or more TFS work items to the check-in change set.
The following system requirements must be met:
To set up Work Items
To Use Work Items
This change set will now be linked to the selected work items.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center