I have a situation where we have six projects in a VS 2008 solution. They have a dependency tree similar to the following:
A depends on B
B depends on C, D, E, F
C depends on F
D, E, and F have no dependencies.
When I look at the "Build Order" tab in Project dependencies for the
solution, everything looks kosher: F, E, D, C, B, A build order.
When I execute the build from the command line (using our continuous
integration tool), the build is started in the correct order; however,
it is started in parallel. That is the log shows build items from F, E,
D, C intermingled. Unfortunately, C completes its build before F is
complete and thus errors occur. And, in fact, when fast building
projects D & E complete, Visual Studio starts B and A, resulting in
even more confusion as dependencies in F and C are incomplete.
How do I force Visual Studio to wait for the completion of dependencies before beginning work on sub-projects?
(Use of Visual Studio 2005 is forced on us for this project due to delivering the project on older CE environment.)