Teamprise 3.3.0 Release Notes

Command-line Client

Previous versions of the CLC disallowed the combination of the -server and -profile options. 3.3 uses the -server option's value to override the server URL stored in a named profile. Use of both options is required when the workspaces command is used to update the computer name in workspaces (-updateComputerName) and proxy configuration from a profile must be used. The section about profiles in the CLC user guide was updated to describe this change.

General

Teamprise clients no longer require activation.

The BeanShell tab was removed from the Teamprise Support dialog. The feature was not being used during Teamprise support cases and removing the tab allowed us to ship one less dependency.

Prior versions of Teamprise clients performed poorly when adding Mac packages (.xcodeproj packages, for example) to source control when the packages were added as files instead of folders. Packages are now treated as folders even in a file context.

Kerberos-based authentication is available for 64-bit Mac OS X (10.6 and higher only) installations.

Prior versions of Teamprise clients would not always remove files properly from labels. Numerous improvements have been made to the label editing dialog to improve label coherency.

The .tpattributes file can be used to create symbolic links with local path targets. The "link" attribute requires server paths, "local-link" requires local paths. See TKB00037 Teamprise Extended Attributes File for details.

The file encoding (as stored in Team Foundation Server) can be changed in Teamprise Explorer and Teamprise Plug-in for Eclipse in the file properties dialog.

Prior versions of Teamprise clients would not render some Work Item controls when running in AWT headless mode. All work item controls are now displayed.

Plug-in for Eclipse

In prior versions of Teamprise Plug-in for Eclipse, certain functionality was disabled from Source Control Explorer when no Eclipse projects were mapped to Team Foundation Server. All functionality is now available via the Source Control Explorer.

In prior versions of Teamprise Plug-in for Eclipse, the Teamprise Import Wizard would fail to import projects that had been part of a case-changing rename. This limitation has been removed.

Some controls and dialogs trigger bugs in the Eclipse 3.5 Cocoa port. These dialogs and controls have been disabled until fixes or workarounds are available.

Team Foundation Server 2010 Beta 2 Compatibility

TFS 2010 allows different reporting services configurations per team project within a team project collection which we now support when talking to a TFS 2010 Beta 2 server or above. Note that this functionality has changed since TFS 2010 Beta 1 so attempting to connect to a Beta 1 server will result in an error for the Reports node in Team Explorer.

TFS 2010 allows for different portal configurations per team project with a project collection, including non-sharepoint based portals which we now support in Team Explorer and also when locating the process guidance for work items.

The introduction of Project Collections in TFS 2010 also means that a new URL syntax is required when connecting to TFS. Previously, TFS services were all derived from the base URL in the format "http://tfsserver:8080/". In the 2010 release TFS is installed by default in a "tfs" virtual directory and all services are resolved relatively from the URL of the project collection. Therefore, to connect to a TFS 2010 server the URL syntax is now "http://tfsserver:8080/tfs/DefaultCollection" where "tfsserver" is the name of your TFS instance, "tfs" is the virtual path in which the TFS application was installed and "DefaultCollection" is the project collection name.

New link types have been introduced in work item tracking in TFS 2010 along with the ability to provide customized link types. Previous versions of Teamprise would not be able to display any of the work item if it contained a link type that Teamprise did not have explicit support for. Teamprise will now display work items that contain unknown link types and will display the link, however the unknown links will not be editable.

Team Foundation Server introduces a new version of the Work Item Query Language (WIQL). Teamprise 3.3 does not contain support for the new WIQL statements, however un-parsable queries will be highlighted with a little red error in the icon for the query. In addition a human readable error message is provided in the event that a user attempts to run a work item query that Teamprise 3.3 or cannot parse.

The default process templates in TFS 2010 allow for several new work item controls. Read-only implementations of the Associated Automation Control and the Test Steps Control are provided to allow Teamprise users to create, modify and read work items using the new controls. The Repo Steps Control is provided, however links to material related to the steps (such as video attachments, screen shots etc using a vsts:\\ based link) will not download the linked content. Viewing of work item attachments works as in previous version of Teamprise. Any hyperlinks in labels are ignored and Teamprise does not currently provide a version of the Web Page Control.

TFS 2010 provides a new easy basic installation mode that will install TFS without requiring the Sharepoint and Reporting Services dependencies. When connecting to a basic installation, Team Explorer will now not show the Documents and Reports Nodes for team projects that do not have these services configured.