I am currently involved in a ASP.NET project with about 40 projects in the solution. We are doing all our development in cloned Virtual PC environments so all developers hav
What we did at our company is to use file reference, so only the changed projects need to be built, and at any given time there is no more than 10 projects in my solution, mostly 2~3 gets built.
We also build our trunk for each check-in, and have batch file for developers to pull the most recent dlls.
Of course, this doesn't stop the painful assembly reference error from happening, but they become more of a nuisance than problem after a while.