For the latest version of the Readme click here.
For Beta 2, the latest version of the Readme is available here.
For Beta 1, the latest version of the Readme is available here.
1.2 Supported Operating Systems:
1.4 Prerequisites:
There are no known issues.
There are no known issues.
In the RC release, Team Foundation Server Proxy will not service download requests from users who connect to it. Users who attempt to use the proxy will get an http 500 or 404 error message, and all requests will be directed to the main instance of Team Foundation Server. Users will also see messages in the console output or Visual Studio output window indicating the proxy was not used.
To resolve this issue:
To proxy requests for version control files with an instance of Team Foundation Server 2010 RC, you must use Team Foundation Server Proxy from the Beta 2 milestone of the current release or Team Foundation Server Proxy from the previous release (Visual Studio Team System 2008 Team Foundation Server).
There are no known issues.
There are no known issues.
There are no known issues.
Some filters that were applied to Beta 2 reports may need to be applied again after an upgrade from Beta 2 to RC. Reports that use these filters are affected: Area Hierarchy, Iteration Hierarchy, Work Item Tree Hierarchy, Version Control File Hierarchy, Test Suite Hierarchy, Build and Build Source Project File Hierarchy.
To resolve this issue:
Apply any of the affected filters that were originally used in Beta 2 reports to the RC reports after the Beta 2 to RC upgrade.
There are no known issues.
After you upgrade Team Foundation Server from Beta 2 to RC or RTM, you may have to recreate your build definitions because of changes in the default build process templates.
To resolve this issue:
Replace (or reconcile) your Beta 2 build process templates with those that ship in the RC/RTM release. You can do this by creating a team project and copying the build process templates into your upgraded team project. If you have customized your build process templates, you will want to merge the RC/RTM build process templates with your customized versions.
There are no known issues.
There are no known issues.
Customers who use an older version of Team Explorer to connect to Team Foundation Server 2010 must apply the Forward Compatibility Update to the older version of Team Explorer. When you attempt to add an instance of Team Foundation Server 2010 to an older version of Team Explorer, you do not get an error message that explains the requirement for the Forward Compatibility Update.
To resolve this issue:
Install the Forward Compatibility Update for Team Explorer 2008 from the following page on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=166481. If you are using Team Explorer 2005, you must wait for the upcoming release of the Forward Compatibility Update for Team Explorer 2005.
Many customers may need to continue to use Team Explorer 2008 to connect to an instance of Team Foundation Server 2010. The Forward Compatibility Update for Team Explorer 2008 will enable Team Explorer 2008 to perform scenarios as it did for previous versions of Team Foundation Server. Several new features in Team Foundation Server 2010 exceed the capabilities of Team Explorer 2008.
To resolve this issue:
To continue to use Team Explorer 2008 with Team Foundation Server 2010, install the Forward Compatibility Update from the following page on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=166481
For a description of supported compatibility scenarios and recommendations, see the following page on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=166507
The URL for connecting to Team Foundation Server has changed for Team Foundation Server 2010. Team Foundation Server 2010 administrators may need to alert users who continue to use Team Explorer 2008 that the URL to connect to Team Foundation Server has changed and that the entire URL must be added to the connection dialog box in Team Explorer
To resolve this issue:
Here is an example URL that uses the default port, the default virtual directory, and a collection that is named Collection1: http://server:8080/tfs/Collection1
Where server appears in the sample URLs, specify the name of the server. Where tfs appears, specify the name of the virtual directory. Where collection1 appears, specify the name of the collection.
For a description of supported compatibility scenarios and recommendations, see the following page on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=166507
Users of older versions of Team Explorer can submit changes that affect a single gated build definitions, but those users will not be prompted with the confirmation dialog box. If the check-in affects multiple gated build definitions, it will fail.
To resolve this issue:
If you are submitting a change that affects a single gated build definition, you will not be prompted with the confirmation dialog box. However, your submission will result in a build getting queued to verify your changes before they get committed to the repository (standard gated check-in behavior). To verify your check in, you can check Build Explorer (just like a user of Team Explorer 2010 would), or you can use the build notification applet (use the 2008 power tools release rather than 2010 release).
If your check-in affects multiple gated build definitions, you have two options when checking in from an older version of Team Explorer:
For a description of supported compatibility scenarios and recommendations, see the following page on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=166507
Users who have Visual Studio Team System 2008 or an older version of Team Explorer can create but not edit existing build definitions, even those that were just created.
To resolve this issue:
Use Team Explorer 2010 to edit build definitions, or use a text or XML editor to edit the build process template.
For a description of supported compatibility scenarios and recommendations, see the following Web site: http://go.microsoft.com/fwlink/?LinkId=166507
Although users of Visual Studio Team System 2008 can use the "Manage Build Agents" dialog box to manage build agents when connected to Team Foundation Server 2010, those users cannot modify the properties of a build controller for Team Foundation Server 2010. If they attempt to modify the properties of a build controller, the following error message appears: "Updating build agents is not supported from this client. Please use a client compatible with Team Foundation Build Codename Rosario and try again."
To resolve this issue:
Use Team Explorer 2010 to modify the properties of a build controller for Team Foundation Server 2010.
For a description of supported compatibility scenarios and recommendations, see the following page on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=166507
© 2010 Microsoft Corporation. All rights reserved.