You should consider the built-in membership element as a black box - expanding a stock membership scheme is a pretty bad idea overall.
The profiles are pretty ugly to be honest - kind, if you are comfortable with storing different settings, but I would really like to store the data that I at one point cared about extracting. The main problem is that it stores material in an opaque serialized field, so it is difficult to extract data. Overhead can be frustrating because they will deserialize this material for every request, so if you have an extensive profile, it can become expensive. And in most cases, you should not extract unnecessary profile information for each request.
Regarding usage, I would start from the MSDN page . Also note that MVC has additional problems - it is not directly connected to this stack, although it can still be used.
All that said, you probably want to create your own member profile table. You will probably double some data with built-in membership bits, but that's fine. You need to set up this table with some kind of membership attitude - I prefer using the owner identifier structure rather than directly linking it to accounts, as this makes things much more flexible. For example, it allows users to have multiple profiles, if necessary.
source share