Open justSteve opened 11 years ago
The CustomIdentityStore constructor accepts an IdentityDbContext which is a regular entity framework DbContext.
One way of integrating your object model would be to have your DbContext inherit from an IdentityDbContext and pass that to your CustomIdentityStore. But just so you know, there are a lot of breaking changes in the RTM version from the RC version. The IdentityDbContext has changed into a context that require your User class to inherit from a new IdentityUser class.
Question for you Onybo, where do you find this information on how to implement these features, and about the changes from RC to RTM? I'd like to read and know the same info so that I can work on some of my own customizations for a POC of a new MVC5 site using Identity for registration.
The RTM assemblies can be found here: https://www.myget.org/gallery/aspnetwebstacknightly
When you have the assemblies Ilspy, Reflector or Dotpeek provides info.
On Thu, Sep 19, 2013 at 6:52 PM, Josh Simerman notifications@github.comwrote:
Question for you Onybo, where do you find this information on how to implement these features, and about the changes from RC to RTM? I'd like to read and know the same info so that I can work on some of my own customizations for a POC of a new MVC5 site using Identity for registration.
— Reply to this email directly or view it on GitHubhttps://github.com/onybo/Asp.Net-Identity-RC1-sample-app/issues/1#issuecomment-24754804 .
Curious as to your thoughts on the workflow to that integrates these membership management features into a wider object model. You project demonstrates a CustomerUserStore but does so without employing the conventional POCO classes typical of EF projects.
I'd like to use EF's Migrations approach to integrate my object model with the Identity entities but it's not obvious how to scaffold that. Welcome any thoughts and thanks for the initial project.