title: Install-Package & NuGet Package install location - where installed to?
body: <pre><code>&gt; nuget                                                                                                         
  nuget : The term 'nuget' is not recognized as the name of a cmdlet, function, script file, or operable program. ...
  
  &gt; find-package -name nuget | Install-package -verbose
  VERBOSE: Skipping installed package NuGet 1.3.3.
  
  &gt; nuget                                                                                                         
  nuget : The term 'nuget' is not recognized as the name of a cmdlet, function, script file, or operable program. ...
  </code></pre>
  
  <p>If it is installed, where is it installed?  I searched across the drive and no other copies of <code>nuget.exe</code> exist except for the one I manually installed (but which is obviously not in the $PATH so surely it is not referring to that - I renamed it to double-check!).</p>
  
  <hr>
  
  <h3>Question update</h3>
  
  <p>I had an expectation from my Java experience and it seems like I was asking the wrong question.</p>
  
  <p>My use case is below.  Background first.</p>
  
  <ul>
  <li>I am new to MS App development though have a decade of Java dev experience.</li>
  <li>(Where i currently are) there is an old version of ASP.Net application that won't work with the <code>dotnet</code> cli.</li>
  <li>The team here had hard coded (saved) dependencies and also created their build system to expect to find other dependencies such as in a Visual Studio install.  Having my background I don't like this expectation, especially when it comes to scaling.  </li>
  <li>The existing build system uses <code>MSBuild</code> and makes use of <code>.targets</code> files</li>
  </ul>
  
  <p>My use case is to run a build using defined (NOT PRE-DOWNLOADED) dependencies and on a server that has no expectation about the build environment apart from some key tools.  Visual Studio is an IDE and I don't expect to find this on a server.</p>
  
  <p>I have created dependencies in a <code>packages.config</code> file.  I want to add <code>nuget.exe</code> to the build script (currently a <code>build.bat</code> but a powershell equivalent is preferred).</p>
  
  <p>I know there is a lot of information out there, but with my lack of knowledge in this area tied to the fact that what I want to do is rooted somewhere around 2012 (I'm guessing), I'm not sure what to do.</p>
  
  <p>Given what I do know, I thought all I wanted to do is:</p>
  
  <ol>
  <li>Install <code>nuget</code> at the start of the <code>build.bat / build.ps1</code> script</li>
  <li>Run <code>nuget</code> to install the defined dependencies
  
  <ul>
  <li>I have downloaded <code>nuget</code> manually, run <code>nuget restore</code> and confirmed that it does what I want</li>
  </ul></li>
  <li>Run the build as before</li>
  </ol>
  
  <p>The first attempt at asking this question was to address #1 from this list.  I thought powershell could be used to download <code>nuget.exe</code> and then the build script could call <code>nuget restore</code>.</p>