Team Development with Visual Studio Team Foundation Server

3. Add the following section just before the closing
element in TFSBuild.proj:
true
true
false
These settings accomplish the following:
• SkipClean. Setting SkipClean to true ensures that the build will not clean out the
local build and sources folder.
• SkipInitializeWorkspace. Setting SkipInitializeWorkspace to true ensures that the
build will leave the existing workspace in-place for the build machine.
• ForceGet. Setting ForceGet to false ensures that the build will only get updated
source, rather than getting all source for the workspace.
Additional Resources
• For more information, see “Practices at a Glance – Team Build” in this guide.
• For more information about configuring an incremental build, see “How to:
Configure Team Foundation Build for an Incremental Build” at
http://msdn2.microsoft.com/en-us/library/aa833876(VS.80).aspx
Avoid Synchronizing Redundant Folders in Your Build
You should scale down your workspace mapping or cloak folders that are not needed as
part of the build.
When you execute a Team Build, the server retrieves all of the files it needs from source
control. The files that are retrieved are defined by the workspace that is used to create the
Team Build Type. Some of the files that are mapped into the workspace may not be
needed. You can change your workspace definition to reduce the folders included, or you
can cloak unnecessary files so that they are not retrieved as part of the build.
For example, the default mapping for a new project is $/TeamProject. If all your source
files are under $/TeamProject/foo/bar/foobar/sources, you should map only that directory.
To cloak files beneath your workspace mapping, you can edit the
WorkspaceMapping.xml file that is created when the Team Build Type is created and is
used to define the folders that are retrieved when performing the build. You can cloak
files and folders that are not needed as part of the build. Folder cloaking is preferred
because individual file cloaking can introduce maintenance overhead.
To cloak folders
1. Check out WorkspaceMapping.xml from source control.
2. Add the appropriate cloak entries to this file.