title: Managing Nuget packages for C# project present in multiple solutions
body: <p>I am now on the phase of <strong>refactoring madness</strong> of a big project which has a lot of <strong>legacy and unstable modules</strong>. I've decided to <strong>split the solution</strong> that currently has ALL projects (so around 20 and there will be more because of unit test projects that would surely come in next months) chained in it to make it more independent and granular. </p>
  
  <p>With this approach there are modules e.g. API clients that needs to be either referenced or added in multiple solutions. </p>
  
  <p>The problem is that Nuget packages are getting restored only on the solution that it was added originally for the first time. So the simplest example:</p>
  
  <p>Solution A:</p>
  
  <p>------ ProjectA</p>
  
  <p>------ APIClient</p>
  
  <p>Solution B:</p>
  
  <p>------ ProjectB</p>
  
  <p>------ APIClient</p>
  
  <p>Since we are not including packages folder it causes problems with Nuget packages:</p>
  
  <ol>
  <li><p>Clone the repo.</p></li>
  <li><p>Open Solution B, build it and restore the Nugets for solution.</p></li>
  <li><p>Errors with packages of ClientAPI in Solution B.</p></li>
  <li><p>Go to Solution A build it and restore the Nugets for solution</p></li>
  <li><p>Get back to Solution B.</p></li>
  <li><p>Nugets are restored for ClientAPI in Solution B and errors are gone.</p></li>
  </ol>
  
  <p>Is there a way to somehow:</p>
  
  <ul>
  <li>Make the project using different path for each solution?</li>
  <li>Maybe chain solutions in build to make Solution A always build with Solution B? But that sounds like loosing some benefits of splitting this one big solution to smaller ones.</li>
  <li>Use any other approach to make it more granular and yet do not suffer problems with the necessity of rebuilding all? I've heard of private Nuget feeds, would that be an answer to this problem if my config allows that?</li>
  </ul>
  
  <p>My config:</p>
  
  <ul>
  <li>VCS: TFS with TFVC</li>
  <li>IDE: Visual Studio Proffesional 2017 </li>
  <li>Default package management format: Packages.config</li>
  </ul>