mapping - TFS build-server build of branch? -

We have a TFS 2008 project with two branches ("Main" and "Newfuture"). Each source code has a complete, independent "copy" (version).

By changing workspace mapping, we can either mapping the version on our local PC and working with both the branches with both problems.

However, if I set up mapping to switch to our build server on the newfire branch (which should be swapped in the newfire source code without changing anything which is related to the buildform) Errors are found: There is no work folder mapping for

$ / Main / Product.sln

when it is made up of the newfactor branch Still looking at anything in the Main branch, even if this Khana should have no reference anywhere in the source code. It seems that there is no reference caching for Maine !!

I have a completely clean build (removed the build folder from the server and / p: Fly through the mapping server to run the build with ForceGet = true, and on any server There is also no file that can cache the workspace binary), but it does not help.

Any suggestions?

Verify that:

• $ (SolutionToBuild) is a relative Path uses when the product.sln refers to
• The relative path between the $ / newfire /.../ TFSBulged. Proj and $ / newfactor / product. Sln is similar because it is the main branch Is in.

/ edit

Note, however, it is important to not not that $ / main and $ / branches / feature trees in a hierarchy At the same level, there should be local path on the build path. * What is under each branch in all these cases if content is intrinsically consistent then all your existing build scripts should work without modification.

<

My method is not the only way, but I can prove that it works better than all other changes made by me over the years :) < / P>

* Clearly, trying to facilitate team builds can be a lot more painful than the proposed restructuring for your MSBuild script, You have to keep somewhere ... If you own> 1 build server (or may be in the future) then you have to consider the strategy of deployment of a change ... you need the meta-SCM process to get your SCM process management of!