title: How to set dynamic path to nuget references?
body: <p>Here is the sample project structure:</p>
  
  <pre><code>{ ProjectA }
      { packages } &lt;-- packages are created here
      { ProjectA }
          - ProjectA.csproj &lt;-- references ProjectB and C.
          - packages.config
      - ProjectA.sln &lt;-- contains all projects: A, B and C.
  
  { ProjectB }
      - ProjectB.csproj
      - packages.config
  
  { ProjectC }
      - ProjectC.csproj
      - packages.config   
  
  *{ packages} &lt;-- *When I manually paste packages here. So one level above ProjectB.csproj file, then ProjectB compiles.
  </code></pre>
  
  <p>ProjectA solution has all three projects: A, B and C. ProjectA reference ProjectB and ProjectC.</p>
  
  <p>When I compile ProjectA (projects B and C are compiled as well), all nuget packages are downloaded into {packages} folder on the same level as solution file. The problem is that ProjectB is not compiling. Yes... only ProejctB. I'm not even gonna investigate why only one project compiles although their configuration is exactly the same. Anyway...</p>
  
  <p>In both ProjectB and C, when I expand References dlls from nuget are seen as they were missing (with the yellow rectangle). Somehow ProjectC compiles anyway, but ProjectB doesn't. The errors says it can't find the reference which is clearly in the packages folder.</p>
  
  <p>My question is, how do I program/configure that sentance (psuedo code):</p>
  
  <p><strong><em>"Dear ProejctB, Please look for the references in the package folder generated on the same level as the solution file. The solution file, which is trying to compile you right now. Thank you"</em></strong></p>
  
  <p>PS. So technically, the path to the dll (reference) will be kinda dynamic. It will change depending on which solution file is opening/compiling the project. Is it possible?</p>