Teamprise 3.1 Release Notes

Command Line Client

The add command previously did not properly canonicalize relative local paths given as free arguments (for example, "./directory/file.txt") causing the Team Foundation Server to reject the add in certain circumstances. Teamprise 3.1 now properly formats these paths.

Teamprise 3.1 now accepts edit and submit as command names. These commands function exactly like the "checkin" command.

The help text for the profile command now documents the httpProxyIgnoreGlobal profile setting and its interaction with the HTTP_PROXY environment variable.

Teamprise 3.0 printed a NullPointerException when the shelve command was run with no pending changes. The CLC now prints the correct message.

Output from previous releases was missing a colon after the "Date" field. The colon is now present.

The help text for the profile command now documents the tfProxyIgnoreGlobal profile setting and its interaction with the TFSPROXY environment variable.

Previously only local paths were accepted.

Previous versions did not display any check-in policy override information in the detailed history command output. Teamprise 3.1 now displays this information.

Previous versions of the Teamprise CLC printed each directory name as its first child when the get command was run. Now only the names of each directory's children are printed.

Previous releases only accepted server paths when the cloak and decloak options were given for the workfold command. Teamprise 3.1 also accepts local paths.

Teamprise 3.1 now correctly uses the paths given as free arguments to the unshelve command to find the correct cached workspace if no explicit workspace is specified. This fix may have also improved the detection for other commands that shared the same cached workspace search code.

The output of the workfold command now shows the server path for one-level working folder mappings with a text suffix of /*. An example one-level mapping would now show $/Project/directory/* as the server part instead of $/Project/directory.

Previous versions of the Teamprise CLC recommended the use of the server option to discriminate between ambiguous cached workspace names, but this option's value was not used correctly. Teamprise 3.1 now uses this option value to select only the cached workspace that matches the given value.

Teamprise 3.0 fully supported profiles (through the the profile and profiles commands and the profile option) for version control CLC operations. In Teamprise 3.1, these commands are also supported for use with the work item tracking command-line client (wit).

Teamprise 3.0 supported brief and detailed format types for many commands, brief being the default value in all cases. When CLC output was parsed by a program, the brief format often omitted important information and the detailed output still occasionally truncated very long strings to fit text on one screen. Teamprise 3.1 supports an additional xml mode wherever brief and detailed modes were previously available. Text is never truncated in the XML output mode so it is suitable for scripting and automation.

CLC and TFS errors are not included in the XML output. Errors are printed to the standard error stream and the exit status of the CLC should be checked for success before parsing the standard output as XML.

Eclipse 3.4 Support

Check-in policy failures would be correctly detected in Eclipse 3.4, however the failure messages would be displayed in a zero-width column to the end-user making them very hard to find. In Teamprise 3.1 the policy failure messages will take up the full width of the available space in the policy warnings tab.

If a user who had no Teamprise license installed attempted to import a project from Team Foundation Server before the license was loaded than a Null Pointer Exception would be throw. This had been fixed.

Teamprise now contains x64 compiled version of the associated native code libraries meaning that Teamprise can be used in a 64-bit version of the Eclipse IDE running on a suitable operating system with a 64-bit Java runtime.

General

Teamprise 3.1 corrects an error in our automerge utility where a specific category of a three-way merge could not be resolved and would lock up the automerge utility. In addition, our automerge utility better detects file encoding for files which contain a Byte Order Mark (BOM).

A internationalization issue has been fixed whereby the Documents node in Team Explorer was not available for team projects that used certain valid UTF-8 characters in the name.

External compare tools can now be invoked when performing a comparison on two folders.

When using Teamprise Explorer 3.0 with a global HTTP proxy configured, there were some issues in the persistence and re-use of the proxy details between sessions. These have now been fixed with the move to the Eclipse 3.4 codebase as a basis for Teamprise Explorer.

The integration into the Eclipse Package Explorer has greatly improved support for drag-and-drop and cutting and pasting resources.

Teamprise now correctly authenticates with http proxy servers requiring NTLM or NTLMv2 authentication, such as Microsoft ISA Server.

Numerous small bug fixes and performance improvements have been included in this release including fixes from issues reported by customers using the 2.x and 3.0 versions of the Teamprise Client Suite.

A number of small issues when using Teamprise with Rational Application Developer Version 6 (RAD6) were fixed in this release.

Teamprise Explorer has now moved from the Eclipse 3.3 to the Eclipse 3.4 codebase. This fixes a number of minor display issues, especially on the Mac OS X platform.

Offline Support

Teamprise Explorer is able to detect changes which were made to resources outside a Team Foundation Server client. Any changes made while offline will be pended to the server.

The Teamprise Plug-in for Eclipse is now able to work on a Teamprise-managed project without a connection to the Team Foundation Server. If a connection cannot be established, the user is now prompted to enter "offline mode", where changes to local resources may be made without notifying the server. When the Team Foundation Server becomes available, the user may "return online", and any changes made will be detected and pended to the server.

TFS 2008 SP1 New Features

When available on the server (i.e. TFS 2008 SP1 and above), Teamprise will now display the last check-in date and time for the particular file or folder. Note that when connected to a server that is running a version of Team Foundation Server prior to TFS 2008 SP1 then this column wil always be empty. For more information see the following blog post from Martin Woodward, Last Check-in Date Explained.

In Team Foundation Server SP1, a new feature was introduced that allows for the filtering of meta-data sent to the client based on the credentials of the user connecting and the user-agent connecting from. Teamprise 3.0 works with the new feature; however some performance issues were discovered which have been rectified with this latest release.

When available on the server (i.e. TFS 2008 SP1 and above), Teamprise now supports the checkin option to the branch command in the Teamprise Command Line Client. The allows a new branch to be created and checked-in from a single command and is significantly faster for large branch operations.