Have Geek Brain

C # ASP.net profile or membership table setup

what's better?

use a profile table to store information that is not present in the membership table (like country, age, etc.) or customize the membership?

thanks

+2


a source to share


1 answer


Membership data should generally consist of information related to authentication. that is, security.

A profile is usually a suitable place to store user metadata. those. personalization.

These two types of data serve different purposes, and segregation allows for a clear separation of concerns among suppliers.



An exception to this could be considered if there is some non-standard metadata that is directly related to authentication / authorization.

It is best to use built-in providers whenever possible. This reduces the amount of code you have to develop, implement, test, and maintain. And membership, that is, security, is not what you want to find in it.

So, I would consider using a tried and tested and true membership provider, and if you want to use table based metadata use a custom profile provider like http://www.asp.net/downloads/sandbox/table-profile-provider- samples

+1


a source






More articles:


All Articles