I installed .net core from this site. Playing with it led to a number of related package management questions:
dotnet restore
command proceeded to "install" .net core NuGet packages. Where were those packages "installed"? A new folder was not created.dotnet restore
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 restore
also would have grabbed very little (three or four packages, not a hundred). Why this behavior?dotnet restore
. 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 dnxcore50
. Why this behavior? restore
command were listed as beta. Odd. I thought .Net Core was in RC1, not beta. Confused by this. Why this behavior?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?).
Update:
In NuGet 3+, you can use the NuGet CLI's following command to get the global-packages folder location
nuget locals global-packages -list
Check out following links for more details about NuGet
https://docs.nuget.org/ndocs/consume-packages/configuring-nuget-behavior
https://docs.nuget.org/ndocs/tools/nuget.exe-cli-reference#locals
The default ASP.Net template has so many packages. Since you tried first time, it tried get all those 100s of packages
You already had those packages in your nuget global locations, it skipped the restore.
Delete all contents under packages folder (location indicated in 1)
Some of the beta packages are there. You can go to project.json file (available under the web root) and play with the dependencies section.