(This question was lurking as an answer here)
What are the advantages of having projects in the same solution if you use file references?
In answers to this question about structuring large applications, several people mentioned having a 'monster' solution for the automated build (at least), and then developers each building their own custom ad-hoc solutions.
My understanding is that having a 'master' solution allows VS to work out the build order correctly - but that surely requires project references, doesn't it?
And if that is the case, it is all well and good making custom mini-solutions, but if you mess with the project dependencies (which you will have to if you want to compile), that will mess them up for the master solution too.
What am I not getting here?