Although many scenarios have been enabled in the VSTS Beta 1, there are a number of compatibility issues which are still being working on.

 image

 * List of Known Issues and Workarounds

1) Team Foundation Server 2010 administrative functions are only supported using Team Explorer 2010.

Problem Statement

As Team Explorer 2008 and Team Explorer 2005 are not aware of several Team Foundation Server 2010 features, administrative functionality has been limited to Team Explorer 2010. For example, the administrator can only run the Project Creation Wizard from Team Explorer 2010 to add Team Project to Team Foundation Server 2010. Team Explorer Team Explorer 2010 client can also be used to administer the Team Foundation Server 2008 server.

Workaround

Use Team Explorer 2010 to perform administrative functions on Team Foundation Server 2010.

2) How to connect a Team Explorer 2008 SP1 to a Team Foundation Server 2010 Server

Problem Statement

Team Project Collections, new to Team Foundation Server 2010, change the path to the server.

Workaround

We can express the connection string as follows:

http://<serverName>:<port>/<vdir>/<collectionName>

Where the <vdir> is an optional, server level argument.

Example connection Strings looks like: http://myserver:8080/Collection1 or http://server:8080/tfs

Moreover customers can give the server name (using the Team Explorer 2008 way to create the connection string) to connect to default collection of the instance on that server.

3) How to connect Team Explorer 2010 to Team Foundation Server 2008

Problem Statement

The path field in the connection dialog is defaulted to Team Foundation Server

Workaround

Team Explorer 2010 connection dialog may need the path field cleared to connect to a previous version of Team Foundation Server.

image

4) Test Results Publishing is not supported for a Team Explorer 2008 SP1 or older clients.

Problem Statement

Test case results cannot be published using Team Explorer 2008 or older clients.

Workaround

Use Team Explorer 2010 to publish test case results.

5) Rename in Version Control is not supported for Team Explorer 2008 SP1 or older clients.

Problem Statement

Rename in Version Control can cause unexpected results using Team Explorer 2008 or older clients.

Workaround

Use Team Explorer 2010 to use rename in Version Control.

6) Work Item Tracking Queries with new functionality are not supported for a Team Explorer 2008 SP1 or older clients.

Problem Statement

Work Item Tracking Queries with new functionality create unexpected error messages.

Workaround

Place new queries with linking, grouping, categories, or field comparisons in a separate folder marked “New Clients Only” so customers using Team Explorer 2008 SP1 or older clients can distinguish those queries without these features.

image

7) Navigation to Reports is not supported for a Team Explorer 2008 SP1 or older clients.

Problem Statement

Team Explorer 2008 SP1 or older clients do not recognize the path to the reports for a Team Project hosted on Team Foundation Server 2010.

Workaround

Use a browser to navigate to the http://<reportserver>/reports then click on the “Team Foundation Server Reports” folder and the Team Project Collection folder for the appropriate collection that contains the Team Projects you are interested in.

8) Navigation to non-default Shared Document, Project Portal and Process Guidance locations is broken for a Team Explorer 2008 SP1 or older clients.

Problem Statement

Administrators are able to configure the location of the Shared Documents, Project Portal and Process guidance but Team Explorer 2008 SP1 Client will not be able to find the new location.

Workaround

If the Shared Document, Project Portal and Process Guidance locations have been modified, URLs to the new locations can be sent to the customers with Team Explorer 2008 SP1 Clients or older clients.

9) Microsoft Project plan documents created using a Team Explorer 2010 client, break when opened from a Team Explorer 2008 or older client.

Problem Statement

Customers who open a Microsoft Project plan created from a Team Explorer 2010 client with a Team Explorer 2008 or older client will cause the plan to become unusable.

Workaround

Do not port project plans to other Microsoft Project tools using older client add-ins during Beta 1.

10) Team Explorer 2008 or older client will not be able to manually queue a build without having the “View Build Resources” permissions.

Problem Statement

Build permission on upgrade were not automatically set to enable Team Explorer 2008 or older client users.

Workaround

Contact the Team Project Administrator to have the build permissions elevated for Team Explorer 2008 client users, if no build agents are visible in the Queue Build dialog in Team Explorer 2008.

11) Team Explorer 2008 or older clients will not be able to manage build resources using the “Manage Build Agents” dialog box.

Problem Statement

The “Manage Build Agents” dialog box disabled for the old client user and users get the following error message when trying to edit, add or delete: “Updating build agents is not supported from this client. Please use a client compatible with Team Foundation Build Codename Rosario and try again.”

Workaround

Use Team Explorer 2010 to manage build resources.

12) Team Explorer 2008 or older clients will be able to submit changes that affect gated build definitions, but they will not be prompted with the confirmation dialog and, if their check-in affects multiple gated definitions, it will fail.

Problem Statement

The customer may not know if they were successful or not.

Workaround

The customer can check the build explorer (just like a Team Explorer 2010 user would) or use the build notification applet (2008 power tools release rather than 2010 release).

13) Team Explorer 2008 or older client users can create new build definitions but they will not be able to edit them or to edit other, existing build definitions.

Problem Statement

New build definitions will be automatically upgraded to Team Foundation Server 2010 build definitions using the upgrade build process template, so Team Explorer 2008 or older client users will not be able them.

Workaround

Use Team Explorer 2010 Client to get the WF designer experience or to edit build definitions or use a text or XML editor to edit the build process template.