title: What is the proper approach for multiple solutions and Nuget distribution
body: <p>I currently have a nice solution that works well with all projects included.  The problem occurs when I want to separate and distribute Nuget packages - one to group A, one to group B and so forth.  I've tried to separate all the individual projects into their own solutions and it works great! Great for handing off development tasks, for the separation of duties but hell in debugging, organizing and development time.  I'm wondering if there is a industry view that is being used to solve this byproduct of multiple solutions? (other than the Microsoft multiple solutions article <a href="https://msdn.microsoft.com/en-us/library/ee817674.aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/ee817674.aspx</a>)  A Solution of Solutions of sort.</p>