how to develop asp.net in a team using TFS when adding a referance breaks others builds when they get latest version?

What is the best practice for not breaking builds for team members working on asp.net website code base using TFS?

I keep seeing a single developer adding a reference to get their code to work and checking it in, then when everyone else gets 开发者_开发问答latest version they lack the reference on their dev machines and get broken builds and have to waste time hunting for resolutions.

Aside from emailing the team when someone adds a new reference is there something inherent to VS that can be used?

Can we pull a separate project and refer to that as a redundancy and keep all resource dlls and references there?

---

The Visual Studio Team Foundation Server Branching Guide 2010 describes many working scenarios. It's long but worth reading.

Guidance for Structuring Team Projects

I've always kept third party DLLs in a project folder under source control, so that a get-latest pulls them down.

Of interest?: Visual Studio 2010 Quick Reference Guidance