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.
preguntado el 08 de noviembre de 11 a las 16:11
I believe that Visual Studio builds these projects in the order they appears in solution. If you need to adjust the build order of projects you can use Project Dependencies (do not confuse with .NET References). When you add .NET reference from one .NET project to another inside you Visual Studio solution the Visual Studio automatically creates project dependency. To modify project dependencies manually do the following:
- Right-click on the solution in Solution Explorer.
- Select Project Dependencies
- From the drop-down list select project you want to add dependencies to.
- Select dependencies for this project.
Also you can view the resulting build order by switching to the tab Build Order.