I have a regular class library (not a .NET Core / Standard library) that uses the Entity Framework Core.
After installation, I noticed that it seems to be pulling in a whole bunch of NuGet packages that I absolutely don't need to hang on to. My library has nothing to do with ASP.NET, and yet, since I want to use EF, it looks like I have dependencies on parts of ASP.NET.

Will EF Core work correctly if I remove them? I am worried that if my library is used by an ASP.NET application, these dependencies will cause problems.
This is the Microsoft.EntityFrameworkCore.Tools package that causes the installation of ASP.NET. Thus, it seems that if you need to use Update-Database , etc., you should have an ASP.NET dependency. This seems like a very bad idea.

source share