Buck Hodges (Dev Lead for Team Build and all around good guy) has written an article describing the “schema” for the WorkspaceMappings.xml file. This file is used by Team Build to create a valid workspace for the build to run within. It is usually hand edited and maintenance can be error-prone. Bucks guidance goes a long way to clarifying the implementation of this functionality.
“The WorkspaceMapping.xml file is one of the files generated when creating a new build type. Those of you who’ve had to customize a build are probably familiar with the TfsBuild.proj file, which is the top-level file used to orchestrate the build.
The WorkspaceMapping.xml file is used by one of the custom tasks to create the TFS workspace that contains the files to be built. In version 1 of Team Build, you must edit the WorkspaceMapping.xml file in order to change the mappings used by the workspace created for the build (in Orcas, you can do this in the GUI, and this file is no longer generated or used).
There’s no formal schema on MSDN. Here are the rules…” – Buck Hodges
Luckily, this file goes away and a GUI arrives in Orcas.