title: Diffrences .net Framework and .net nugets management
body: <p>When creating a new solution in .net as opposed to .net framework, I've seen some key differences with the management of NuGet dependencies.</p>
  <p>For example, when a project is referencing another project that has some NuGet packages, the referencing project inherits these NuGet packages. This differs from .net framework, where each project should include the NuGet that the referencing project needs.</p>
  <p>Furthermore, when building a class library that references some NuGet package, for example newtonsoft.Json, then this DLL isn't in the build of the class library. The only thing that shows that this build needs the newtonsoft.Json package is in the *.deps.json file.</p>
  <p>This is all new and confusing to me, as I'm used to developing in the .net framework environment. I'm searching for some good documentation that explains this behavior, preferably compared with the .net framework.</p>