Visual-studio – ny best practices for Visual Studio Project/Solution Structure

visual-studio

I've seen a lot of different takes on this subject so I figured if there's a preferred way on this.

Is there any best practices on how to setup Visual Studio Projects and Solutions in regards to multiple solutions for the same solutions?

For example:
Let's say I have a task that calls for a web app, a console application, and a shared business logic library.

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?

Best Solution

Indeed, there are some guidelines for this sort of setup on MSDN. I wrote a short summary in my answer to a similar question on StackOverflow.