Decoupling my own assembly from Microsoft.AspNet.Identity.*

[zam6ak]

Hi

Great project!
But how do you decouple dependency on Microsoft.AspNet.Identity.* if your domain models are in a separate assembly, which is used by many projects?
I would not want to have MyCompany.Domain assembly having to depend on Microsoft.AspNet.Identity.*

For more details, please see:
http://stackoverflow.com/questions/18727317/decoupling-microsoft-aspnet-identity

[rustd]

We will have a doc showing you how to do it by this week. This doc will show you how you can migrate from sql membership as well which is done by using your own domain models

[zam6ak]

Any updates on this?
If the document is available, could you post a link to it please.

[zam6ak]

Bump!
It's been 2 months - any updates on this?
Thanks

[rustd]

You can look at the following example http://www.asp.net/identity/overview/extensibility/implementing-a-custom-mysql-aspnet-identity-storage-provider
In this article the user has written a custom implementation for MySql but you can write one for your own POCO classes and plug them into the Identity system