This is expected behaviour for the versions you've mentioned. Rather than summarising, here's a thorough explanation on stackoverflow https://stackoverflow.com/a/47366401/663647
On Sun, 2 Sep 2018 at 11:00, Greg Keogh <[email protected]> wrote: > Folks, I just resurrected an old utility project that pokes into IIS logs. > I updated the project to Framework 4.6.1 and add the > Microsoft.Web.Administration package. I notice that it adds a total of 56 > packages and about 100 dll files to the build output. > > I see that the bulk of the files have been pulled in through a reference > to NETStandard.Library 1.6.0. Now, this is a full .NET Framework 4.6.1 > project, so why have packages for things like System.Console and > System.Collections been added when they're already in the full Framework? > Is there some trend I'm not aware of caused by the introduction of .NET > Standard? > > *Greg K* >
