| Guidance for Team Foundation Server 2005 |
Guidance for Team Foundation Server 2008 |
| Dual server deployment will support up to 2000 users. |
You can use dual server deployment to support up to 30,000 users |
| Users need correct domain accounts as part of deployment. |
Domain accounts are no longer required, instead you can use the built in machine accounts, such as Network Service account. |
| Use a custom solution to create Continuous Integration builds. |
You can use Visual Studio build triggers to create and configure Continuous Integration builds or Rolling builds. |
| Use automated tests as part of your build to measure the quality of the build. |
It’s easier to build test lists and specify what tests get run as part of a build step. It’s possible to run GUI tests as part of your automated build tests. |
| Build types must be placed in a specific folder in order for them to be recognized by Team Build. |
Build definition project files (tfsbuild.proj) can be stored anywhere in the version control hierarchy. |
| Use a custom solution to create Scheduled Builds. |
You can create Visual Studio scheduled builds without the need for a custom solution. |
| There are a set of check-in policies available out-of-box. |
A new check-in policy is available for broken CI builds. This prevents check-in of code while the CI build is broken. |
| Use the tool converter.exe to migrate from VSS to Team Foundation Server. |
Use the Visual Studio toolkit for building conversion and mirroring solutions between Team Foundation Server and other source control systems – including VSS. |
| Use workspace mapping to define the set of files you want synchronized to your local machine. |
Team Foundation Server 2008 now allows mapping of a folder or file under a cloaked folder, and wildcard mappings so that you can map all files in a folder without mapping sub-folders. |
| Use workspacemapping.xml file to modify workspace mapping. |
The Team Foundation Server 2008 GUI is used to manage workspace mapping, workspacemapping.xml is no longer used. |
| Use the TFS Power Tool to work offline. |
Use the Visual Studio IDE for working offline. |
| Getting the latest version of a file and checking it out for edit are two separate source control operations. |
You can use an option, to automatically get the latest version of a file when you check it out for edit. |
| Customize pre-build steps to get dependencies when referencing project assemblies from a different team project |
The build definition workspace template is managed in the VS GUI and has the full flexibility of a standard workspace, including mapping paths from multiple team projects |
| Use the TFSBuild command line tool to delete builds. |
Use the Visual Studio IDE to stop and delete builds. |