1
votes

Related

Implementing Custom Membership Provider Membership User Issues

Extending a Custom Membership Provider

Question

  1. If i have different SQL table schema for Roles, Profiles should i create Custom Providers for each of these "Role","Membership" and "Profiles". I am definitely sure many users are unhappy with profile fields that default implementation provides. For example below Profile will require a different override of MembershipProvider.CreateUser because mine does not contain a security question, status etc.

table schema

FirstName
LastName
Initial
Address
Company
FacebookId
LastLogin
1
Custom membershipProvider did not change since 2.0, so it's the same as the question I mention.balexandre
@balexandre god users here get carried away by reading the question Title. Could you read the bolded text under question headline?. The example u pointed too sticks to the profile fields defined.Deeptechtons
if you read my answer that I point out on the other question entirely, you will have all your questions answered, soon you mention Custom Provider is up to you to provide the information, the provider only expects the object, it does not care how and where do you get the data from... (btw: good, not God!)balexandre
@balexandre so does this mean i create my own implementations for those base providers since my schema has changed?Deeptechtons

1 Answers

1
votes

You need to create your own Custom membership provider so you can have whatever you want, for that I would point to my own answer on how you can accomplish that

Custom MembershipProvider in .NET 4.0