Trying to grasp the big picture here. This is a Web Forms project using Identity + EF for user management. The default project contains
OK. After working with the project for a few days, I have figured out a few things that might be helpful for future readers:
As @Konstantin said, as a general rule, you should not use both code-first and model-first approaches in the same project. Personally I prefer database-first over both of them, i.e. create a database design and then import it into my EDMX model. I can then make changes to my DB design later and use "Update Model from Database..." command to refresh my model.
AFAIK, migrations cannot currently be used with EDMX models. These only work with code-first approach.
ASP.NET Identity will automatically create all required tables in your database when your website runs for the first time. You simply need to correct the connection string in your web.config file.
You should generally avoid bringing in Identity tables into your EDMX, but if you really need to do that, do not make changes to these entities through EDMX. Simply use
ApplicationUser class in
IdentityModels file to add custom properties to your user class.