.Net Core and NuGet : <p>I <a href="https://dotnet.github.io/getting-started/">installed .net core from this site</a>.  Playing with it led to a number of related package management questions:</p>

<ol>
<li>The <code>dotnet restore</code> command proceeded to "install" .net core NuGet packages.  Where were those packages "installed"?  A new folder was not created.</li>
<li>The <code>dotnet restore</code> for the "hello world" minimal example required about a hundred NuGet packages, where 99% were presumably irrelevant to the "hello world" app.  Granted, a .net native build will remove all that is not needed - but I expected that the <code>restore</code> also would have grabbed very little (three or four packages, not a hundred).  Why this behavior?</li>
<li>I created a second "hello world" project and again ran <code>dotnet restore</code>.  This time no packages were installed at all.  It seems all the packages installed the first time-around went into some global location to be shared.  I thought .Net Core didn't work that way.  I thought .Net Core projects kept all their dependencies locally.  The only framework I targeted was <code>dnxcore50</code>.  Why this behavior? </li>
<li>I would like to "uninstall" all these global packages, and try again (just for learning purposes).  How might that be accomplished?  Remember, as stated in question #1, I don't know where all those files were installed.</li>
<li>Almost all of the packages installed via the <code>restore</code> command were listed as beta.  Odd.  I thought .Net Core was in RC1, not beta.  Confused by this.  Why this behavior?</li>
</ol>

<p>I'm also curious of what documentation could/would have explained all this to me.  I tried googling for each of these questions, and found nothing (perhaps just horrible google-fu?).</p>
