We found a bug in the Release Candidate version of Team Foundation Server which I shall 'report' here. We accidentally found ourselves in the position of having a team build containing two Visual Studio solutions and a project that was included in both solutions. It appears that TFS Build cannot perform builds in this situation. When it gets to the compilation build step for the 'shared' project, if aborts abnormally. The error in the Windows event log reports a SOAP fault caused by a SQL 512 error ......
I've spent some time in the last few days using the Team Build features of Team Foundation Server. I've recorded some observations on this, and also on the Solutions Build Framework (SBF) in an article at http://geekswithblogs.net/cyoung/articles/71713.aspx.