|
Renaming a file in Version Control can cause unexpected behavior.
A user cannot rename a file and then use the old filename until AFTER the renamed file has been checked in. Ideally - use Team Explorer 2010 to rename files in version control.
Publishing Test Results does not work.
Use Team Explorer 2010 to publish test case results.
Microsoft Project Plan documents created using a Team Explorer 2010 client, break when opened from a Team Explorer 2008 or older client.
Do not port project plans to other Microsoft Project tools using older client add-ins
Work Item Tracking Queries with new functionality will not be editable and will not execute.
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. Use Team Explorer 2010 for running and editing these queries.
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.
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.
Navigation to Reports will not work.
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.
Navigation to Documents, Project Portal, and Process Guidance locations is broken.
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.
Team Explorer 2008 or older client will not be able to manually queue a build without having the "View Build Resources" permissions.
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.
Team Explorer 2008 or older clients can create confusion if using gated checkin
Users 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. 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).
The "Manage Build Agents" dialog box does not work.
Use Team Explorer 2010 to manage build resources. |