title: Is there any best practices for Visual Studio Project/Solution Structure?
body: <p>I've seen a lot of different takes on this subject so I figured if there's a preferred way on this.</p>
  
  <p>Is there any best practices on how to setup Visual Studio Projects and Solutions in regards to multiple solutions for the same solutions?</p>
  
  <p>For example:
  Let's say I have a task that calls for a web app, a console application, and a shared business logic library. </p>
  
  <p>I have seen this situation in a 1, 2, and 3 solutions at some time in my career.  This is a simple example; however, what if number of projects grows?  Is there a line when to keep it in one or break it apart?</p>