Geek Answers Handbook

Entity Framework User and Role Management

I have a Visual Studio solution that contains several projects:

  • Domain Classes
  • Data Access Level - containing the database context
  • MVC application.

An MVC application, by default, uses existing classes to manage users, and also has its own ApplicationDbContext. In this case, we have two database contexts.

What is your experience with user management? It would be better if I created my own classes for user management and placed them in the Domain Classes project. I think that it would be much easier to support, and in this case there will be only one DBC context. Another possible problem might be the relationship between existing ApplicationUsers (from the MVC project model) and classes from the Domain Classes project. Or perhaps move the ApplicationUser class definition to a DomainClasses project?

+5
source share
1 answer

I highly recommend MembershipReboot . You have the option to use the built-in UserAccount or use your own.

On the side note, Brock is part of the Thinktecture . In one of the asp.net booths, it was mentioned that the team could simply recommend a third-party identity provider instead of their own role. That was my understanding, but maybe I just hope so. I think it was https://www.youtube.com/watch?v=CMTd5yS-yFE&list=PL0M0zPgJ3HSftTAAHttA3JQU4vOjXFquF&index=2 , but don't keep me that way.

+1
source

More articles:


All Articles