title: Solution: Per application, or per application suite
body: <p>Often multiple applications share a large codebase of libraries that change often in development.  In these cases, I prefer to create a solution named after the suite, and include separate projects for each application and the shared libraries.</p>
  
  <p>Is this a good approach?  How do others structure their code bases for things like a suite of applications?</p>