Custom membership provider or profile provider in asp.net mvc

Question

I am going to the world of asp.net mvc. I have not figured out yet whether it makes sense to use a custom membership provider or to use a profile provider to manage users?

Answer 1

One, membership providers and profile providers fulfill two different goals. The membership provider provides a list of users and authentication features. The profile provider provides a way to store data related to specific applications associated with each user.

If you need a custom provider depends on what type of data warehouse you want to use. Two built-in membership providers allow you to use an Active Directory domain (usually only suitable for developing applications for a corporate intranet) or an MS SQL Server database. One built-in profile provider uses MS SQL. If you want to use a different type of data warehouse, such as a PostgreSQL database, then you will need a custom provider for this particular data warehouse.

Answer 2

Membership Provider - Manages usernames, email addresses, and passwords.

Profile Provider — Manages all other user preferences, such as name and settings.

So, in order to answer your question, you should use both options because they serve different purposes.