I\'m using ASP.NET MVC 5 with a Database-First workflow. I\'ve created the Identity tables (AspNetUsers
, AspNetRoles
etc.) in my existing database
You can resolved this problem by following these steps:
you will find connection string in web.config file.
place this connection string into identity model clsss
I THINK this scenario is not supported by ASP.NET Identity as it needs a DbContext
which extends IdentityDbContext<ApplicationUser>
(or similar).
Why are you forcing Identity into your DB-First context?
You can use a Code-First context for Identity alongside your other DB-First context without problems...