I'm working on porting an asp.mvc application to asp.net core mvc hosted on .net core.
I was excited to see that EF 6.3 can host on .net core, since it looks like the EF -> EF core migration is something that I'd at like to defer (possibly indefinitely).
Looking at Microsoft.AspNet.Identy.* nuget packages, it appears that they don't have dependencies on a particular .net framework (full or core) just on EntityFrameowrk 6.1 or greater.
Other than the purist idea that I should just move everything over to core while I'm in the code, is there any reason I can't have a .net core, .net core mvc application that uses EF 6.3 and Micrsosoft.AspNet.Identy rather than EF core and Microsoft.AspNetCore.Identity?
After some experimentation:
It looks like I was wrong and Microsoft.AspNet.Identy.Owin has a dependency on the full .net framework. So I will revise the question:
Can I use Microsoft.AspNetCore.Identity with Entity Framework 6.3? My key goal here is to avoid biting off the EF -> EF core migration while getting the rest of my codebase moved to core.