shared Eclipse projects were required to be located directly beneath the Eclipse workspace root. This limitation meant that certain project layouts were not supported - for example, placing projects within a strict hierarchy. Teamprise Plug-in for Eclipse 3.2 supports mapping

share the same name, since this is confusing for users who are new to TFS and/or Eclipse. Whenever the term workspace is used, always determine which kind of workspace is being referred to. For the rest of this document, the terms

share or in a system location on a multi-user system). Permissions When Explorer is installed for multi-user access, it is important to set the permissions on the installed files and directories so users cannot modify the installed files

Overview Starting with Teamprise 3.0, extracting the Teamprise installer archives with the built-in Windows archive explorer may corrupt the extracted files. This error happens more often when using the copy/paste method within the built-in Windows Explorer. An error

Overview Teamprise Explorer on Solaris requires the GTK 2 libraries to be installed. These libraries come standard on newer versions of Solaris, but older versions may require manual installation. You can download the source code to GTK 2 at gtk.org

share Team Foundation Server workspaces when run on the same machine when the computer name contains hyphens. Areas Affected All Team Foundation Server workspaces are identified by a name, a computer where they were created, and other information. If your

sharing a project using the Eclipse plug-in. This will automate many of the checks below, however you may whish to manually carry them out during diagnosis. 1. Check that the connection URL's are correct and in the format

shared between all Teamprise clients). The CLC will never automatically update the credentials in a connection profile, and profile credentials will be used when the profile is specified regardless of the value of the TP\_AUTO\_SAVE\_CREDENTIALS environment variable

Sharing server included with Mac OS X, for instance, uses the user immutable bit to mark files as read-only. Enabling User Immutable Bit To enable the user immutable bit on read-only files, set the environment variable TP\_SET\_IMMUTABLE

shared easily with other team members (each member must configure his own Ignored Resources preferences), and these preferences match only the last component of a resource path (the file or directory name at the end) the .tpignore file may be preferred