This project is read-only.

How to Use a Multiple-Solution Strategy

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

If you work on a very large solution requiring many dozens of projects, you might run up against solution scalability limits. In this scenario, you should break your application into multiple solutions, but do not create a master solution for the entire application because all references inside each solution are project references. References to projects outside of each solution (for example, to third-party libraries or projects in another sub-solution) are file references. This means that there can be no “master” solution. Instead, a script must be used that understands the order in which the solutions must be built. One of the maintenance tasks associated with a multiple-solution structure is ensuring that developers do not inadvertently create circular references between solutions. This structure requires complex build scripts and explicit mapping of dependency relationships. In this structure, it is not possible to build the application in its entirety within Visual Studio. Instead, you use TFS Team Build.

Additional Resources

  • For more information, see “Chapter 3 – Structuring Projects and Solutions in Source Control” in this guide.

Last edited Jul 26, 2007 at 7:48 AM by prashantbansode, version 1


No comments yet.