Your official information source from the .NET Web Development and Tools group at Microsoft.
ASP.NET Identity is the new membership system for building ASP.NET applications. To learn more about ASP.NET Identity, please visit asp.net/identity
The new tutorial explains how to migrate an application that uses Universal Providers for user and role management to the new ASP.NET Identity system. The tutorial also focuses on migrating user profile data created using Universal Providers. The approach mentioned to migrate profile data can be used in applications with SQL membership as well. In Universal Providers, the profile data is stored as serialized xml or binary data. Post migration, the profile data can be accessed as properties on the user class. Also serializing/de serializing profile information for each database transaction is prevented.
Once the migration is completed, you can use the new features available in Identity: you can let users log in through their Google, Facebook, Twitter or Microsoft accounts, use OWIN authentication middleware, integrate user profile and application data, and so on. Feedback is welcome and do let us know if you hit issues during migration!
How do you migrate that "Applications" table? ASP.NET identity doesn't handle multiple applications, does it?
@ta.speot.is: Identity doesn't not use the Applications table and hence is not migrated. Handling multiple applications needs to be done by the user
Thank you for your posting.
Could you provide an example to migrate a MVC 3 or 4 project using a membershipprovider to ASP .Net Identy?
@Adrian: We are working on that and it will be posted out shortly