title: Nuget Dependencies not getting installed
body: <p>I am running a private Nuget Server locally on IIS.
  I am creating packages and uploading them all via commadline using nuget.exe (Later on I have to put this on build server, hence the command line). However there is one issue I am stuck at.</p>
  
  <p>I am trying to declare dependencies. I generate the nuspec file in the folder where the .csproj file is there. Then I manually edit the nuspec file to add this under the metadata tag:</p>
  
  <pre><code>&lt;metadata&gt;
      &lt;dependencies&gt;
          &lt;group targetFramework=".NETFramework4.5"&gt;
              &lt;dependency id="DemoProject" version="2.0.0.0" /&gt;
          &lt;/group&gt;
     &lt;/dependencies&gt;
  &lt;/metadata&gt;
  </code></pre>
  
  <p>DemoProject, version 2.0.0.0 is present on the Nuget Server.
  The project I am creating package for, MyProj.csproj does not have the reference to the DemoProject added to it via Visual Studio. It is just at the packing time I want to create the dependency. It sounds strange but is needed for some initial validation.</p>
  
  <p>Then I run pack command:</p>
  
  <p>"C:\nuget\NuGet.exe" pack MyProj.csproj -IncludeReferencedProjects -Prop Configuration=Release</p>
  
  <p>Then I push it to NuGet server using command line.
  When I do an install via command line, then only MyProj package is present at the install location.</p>
  
  <p>When I use Nuget Package Explorer and create a package, I can use the Package Dependency Editor to specify the dependency. It asks for the URL of my local Nuget Server and then adds the dependency. And when I install that package, it works !! </p>
  
  <p>There seem to be no difference in the generated nuspec file in both the cases. 
  Obviously Nuget Package manager is doing something which I am missing out on. </p>
  
  <p>Any hints?</p>
  
  <p>More details: When I create a lib folder in the Package manager console and put my dll manually, lib->net45->MyProj.dll, then when I install the package thus created also "does not" install the dependency. Back to reading documentation again.</p>