We have a Visual Studio 2010 solution that has over 120 projects that reference each other in some way. All inter-project references are project references and not file references which helps Visual Studio determine the project build order automagically. Out of 120, we have a few core projects that are not interdependant on each other and these projects are referenced by the rest extensively. Hence these projects are at the top of the project build order. These core projects have references from the .NET framework, Enterprise Library (and some of them have third party dll file references like a zip utility).
I cannot figure out why these core projects are ordered in a specific way. What is the algorithm for the project build order for non-interdependant projects?
PS: I do understand I can influence this order by creating a fake dependancy using the Dependencies tab of Project Dependencies.