I would like to take advantage of the IdentityDbContext that comes out of the box in Visual Studio templates for ASP.NET Core projects. However, I would like my entities and migrations to live in a shared project to be referenced by different components of the solution (Web, API, background services, etc.). 

My shared database project was going to be a .NET Standard project, but it looks like I'll have to add a reference to `Microsoft.AspNetCore.Identity.EntityFrameworkCore`. It feels weird introducing to a Standard project a dependency on a Core assembly that is specifically for ASP.NET. Will that pose any problems?