Closed kkocabiyik closed 5 years ago
Hello @kkocabiyik ,
What do you mean Entity Framework Identity
?
Z.EntityFramework.Classic
replace EF6
, it's not a third party library. One drawback of this is that other packages need to release a new version compatible with EF Classic
since the signing key is not the same.
So if you still have packages that reference EF6
, it will unfortunately not work for your project unless this package release a version compatible with EF Classic
.
Hello @kkocabiyik ,
This issue will be closed since we haven't heard back from you.
We will be happy to re-open it as soon as you provide more information.
Best Regards,
Jonathan
@JonathanMagnan I think what @kkocabiyik means here is that in order to user Identity with EF, you'll need to add IdentityDbContext<>
class which is found in Microsoft.AspNet.Identity.EntityFramework
. However, installing it also forces to install EntityFramework
which causes the conflict between EntityFramework and Classic.
I am currently facing the same issue. Not sure if there is a workaround
We are trying to combine Entity Framework Identity with Z.EntityFramework.Classic. When we install Identity packages from nuget, it also includes EF. Since Z.EntityFramework.Classic is the fork of orjinal EF the namespaces and classes are duplicated. Thus, it gives the following error on build.
I have tried adding alias to differentiate the namespaces but didn't work out. How can we solve this? Is there any example about this?