Why does the Entity Framework Core NuGet package depend on ASP.NET and Websockets?

Viewed 1018

I have a normal class library (not a .NET Core/Standard library) that uses Entity Framework Core.

After installing it I noticed it seems to pull in a whole bunch of NuGet packages I absolutely shouldn't need to be depending on. My library has nothing to do with ASP.NET, and yet because I want to use EF, it appears I have to have dependencies on parts of ASP.NET.

enter image description here

Will EF Core run correctly if I remove these? I'm concerned that if my library is used by an ASP.NET application that these dependencies are going to cause problems.

It is the Microsoft.EntityFrameworkCore.Tools package that is causing ASP.NET to be installed. So it appears that if you need to use Update-Database etc, you must have a dependency on ASP.NET. This seems like a very poor idea.

enter image description here

0 Answers
Related