Decoupling ASP.NET Identity from the Core Domain Models - Onion Architecture

Question

I am using this sample project (https://github.com/imranbaloch/ASPNETIdentityWithOnion) as my application architecture, in this sample the core is completly decoplied from the i

Answer 1

Okay I have solved this by doing the following:

1. Include a dependency in your Core to Microsoft.AspNet.Identity.Core
2. Implement IUser interface on the AppUser (this interface come from Microsoft.AspNet.Identity.Core).
3. Implement IRole interface on the ApplicationRole.
4. Completely get rid of the IdentityDbContext and inherit only from DbContext.
5. Implement your own version of IUserStore* providing your AppUser
6. Implement your own version of IRoleStore providing your ApplicationRole.

I know that making a dependency on the Microsoft.AspNet.Identity.Core sounds Odd, but we only need the interface IUser which is basically considered as Core Domain Model for your application too.

The Ultimate Idea here is to GET RID OF THE Microsoft.AspNet.Identity.EntityFramework completely.

Interested devs can +1 this, so I can upload a full working sample on GitHub.