Last post Feb 16, 2018 08:44 AM by Brando ZWZ
Feb 15, 2018 02:48 PM|RateFor|LINK
I'm migrating a website from SQL membership to asp.net identity.
I'm using a MSDN paper on the topic. (https://docs.microsoft.com/en-us/aspnet/identity/overview/migrations/migrating-an-existing-website-from-sql-membership-to-aspnet-identity)
So far, I've migrated some of the old aspnet_ prefixed database tables to the new ones, and then deleted the old ones (after inserting data in the new ones). I've deleted old tables that I wasn't specifically told to delete, including aspnet_profiles,
I've also deleted all the stored-procedures that worked with the old tables.
So now, my questions are:
Feb 16, 2018 08:44 AM|Brando ZWZ|LINK
Is the 'entity-framework' something I have to now learn and put in?
Short answer is YES. You have to learn entity-framework.
Since identity used EF to CURD the user data, you have to learn entity-framework. But MS has created a lot of useful manager class to help manage the user table.
If you don't want to implement custom attribute, you could just learn how to use identity manager class to manage the user data.
Do I have to have classes corresponding to the new tables (such as aspnetUsers)?
Yes, Identity used the EF model first to match the user with model.
You should have the user class map with user table.
What happens to all the old calls, such as 'membership.GetUser()' that were in my aspnet code?
All membership method will be replaced by the identity usermanager method.
Have I deleted tables that I should have kept?
I couldn't understand clearly about this question.
After migrating, identity will use the new table instead of the old membership table.