Team Foundation Build and Team Foundation Server Proxy
• Team Foundation Build is a separate product that allows team members to perform builds of one or
more TFS projects.
- These builds are performed from within Team Explorer.
• In order to use Team Foundation Build, you need to install it on either the TFS application server or on
a separate machine.
- Again, you need to install TFS SP1 after installing Team Foundation Build.
- If installing on the same TFS server machine, it’s best to install this before installing TFS SP1.
• Navigate to a folder called \build\ in the root of the TFS server installation media and run setup.exe.
- When prompted, specify the TFSSERVICE account.
• Team Foundation Server Proxy is typically installed on a remote server.
- Its purpose is to speed up TFS Source Control access by caching resources on the remote server.
- You may also use Team Proxy when accessing TFS via a low bandwidth.
- Its primary purpose is to speed up access to all files stored in TFS Source Control.
• Most often, a dedicated Windows 2003 server with IIS 6 and ASP.NET 2.0 is used to act as the TFS
proxy.
- You need to be sure that you have the proper user account created to connect with TFS.
- Install Team Proxy from the TFS server media by double-clicking setup.exe in the \proxy\ folder.
• Team Foundation Build is a separate product that allows team members to perform builds of one or
more TFS projects.
- These builds are performed from within Team Explorer.
• In order to use Team Foundation Build, you need to install it on either the TFS application server or on
a separate machine.
- Again, you need to install TFS SP1 after installing Team Foundation Build.
- If installing on the same TFS server machine, it’s best to install this before installing TFS SP1.
• Navigate to a folder called \build\ in the root of the TFS server installation media and run setup.exe.
- When prompted, specify the TFSSERVICE account.
• Team Foundation Server Proxy is typically installed on a remote server.
- Its purpose is to speed up TFS Source Control access by caching resources on the remote server.
- You may also use Team Proxy when accessing TFS via a low bandwidth.
- Its primary purpose is to speed up access to all files stored in TFS Source Control.
• Most often, a dedicated Windows 2003 server with IIS 6 and ASP.NET 2.0 is used to act as the TFS
proxy.
- You need to be sure that you have the proper user account created to connect with TFS.
- Install Team Proxy from the TFS server media by double-clicking setup.exe in the \proxy\ folder.
TFS Build
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials