title: Using NuGet on multiple solutions project with the same output path
body: <p>I've tried to look at many of the questions asked here about it, but none is exactly like my set-up.</p>
  
  <p>Also, this issue is NOT directly related to Nuget, but it might be part of the solution.</p>
  
  <p>I have a project which consists of a few solutions. All of the projects in those solutions use the same output path.</p>
  
  <p>Example:</p>
  
  <pre><code>-Root
  --Solution1
  --Solution2
  --Solution3
  --OutputForAllProjectsInAllSolutions
  </code></pre>
  
  <p>I want to use NuGets in those solutions. The problem is if I'll use different version of the same NuGet package in each solution, then the each solution will override it's predecessor's reference dlls.</p>
  
  <p>I was thinking of a solution, but I don't know if it's possible and how.</p>
  
  <p>Something like:</p>
  
  <pre><code>-Root
  --Solution1
  --Solution2
  --Solution3
  --PackagesFolderForAllSolutions // can be done with repositoryPath right?
  --OutputForAllProjectsInAllSolutions
  ---NugetPackageVersion1
  ---NugetPackageVersion2
  ---NugetPackageVersion3
  </code></pre>
  
  <p>Is it a possible? Is it a good solution? How to do it?
  If not, any better suggestions?</p>
  
  <p>Thanks in advance.</p>
  
  <ul>
  <li><strong>EDIT:</strong> I wish I could use 1 solution for all, but it's legacy code, and it has too much complexity.</li>
  </ul>
  
  <p>The setup is 1 source-code repository with multiple solutions.</p>