I’m currently developing a web site that will make heavy use of asp.net membership. (Using Umbraco, but that just uses the regular asp.net membership provider).
I want to store some extended information about a user and I’m considering if I should store the information in the profile or in a custom table. Is there any pros / cons to any specific method? Some properties like payment details are more natural to place in the profile, on the other hand, a transaction log seems less natural residing in the user profile (IMHO). Any thoughts on this?
Any experience with asp.net membership?
I’m currently developing a web site that will make heavy use of asp.net membership.
Share
I would just extend the Membership providor to include the additional infromation. You may want to build your a custom membership provider to replace the standard one, it just means inheriting from the standard one and in your case, possibly just a matter of adding addtional members.
I would also personally not ever use the Profile Provider and just extend the Membership provider.