I'm in the process of getting my head around how the new SimpleMembership provider works in MVC 4 with EF Code First. So far I've got everything working pretty well, but I'm running into something I just don't quite understand.
SimpleMembership auto-creates several tables as a result of this line of code:
WebSecurity.InitializeDatabaseConnection("DatabaseContext", "User", "Id", "Email", autoCreateTables: true);
I have a Code First entity called "User" to store all of my domain specific user data. So using the WebSecurity class, I can get the user id I need in various ways and then query my User entity to get to my domain specific data. However, since there are no POCO classes for the "webpages_xxxx" tables that SimpleMembership auto-creates, I can't easily access those via EF. Specifically I'm interested in getting at the webpages_Membership table so that when I have a user ID, I can get at fields like "IsConfirmed", "PasswordVerificationToken", etc.
Common sense says I'd just need to code some POCO classes to represent the table structures, but it feels like there should be something a little more out-of-the-box. Did Microsoft leave us to just code our own POCO classes to represent their table structure or am I missing something?