current community

your communities

more stack exchange communities

Stack Exchange
tour help
careers 2.0
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 2 down vote favorite

I am started looking at ASP.NET Identity Framework. It is powered with Entity Framework 6.

It is using the default database with the number of related tables. AspNetUsers, AspnetUserRoles, AspnetUserLogins, AspnetUserClaims, AspnetRoles, _MigrationHistory

Currently looking in to solution to decrease the number of tables by following that post and this one

After that i need to add my business tables Products, Categories, etc...

So here is my question.

Currently looks like using Code First i can handle User Profiles. But what next, if i need to add a new Business Tables to database do I need to create edmx model and keep all entities there including Aspnet Identity Enitnites?

Is there any way to do that(to switch ASP.NET Identity Framework to use entities defined in custom edmxfile)?

Or may be I have to keep ASP.NET Identity Framework/User Profiles like it is and handle my business tables through custom edmx model?

What can you suggest?

I think it is good idea to handle everything through edmx file so I can made any changes directly in database and then update edmx file and regenerate the Enitites and Datacontext using tt template.

share|improve this question
    
Seems all EF work has been on Code First and Model/Database First have been abandoned. You should be able to all all three in the same project interchangeably at any time. Update the class updates the model and vice versa. And import database items as well. –  Dave May 27 at 22:01
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.