I require some more fields related to users. So whether its good idea to extend MembershipUser class or to create separate class that has relationship (foreign key) with MembershipUser class UserID?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I require some more fields related to users. So whether its good idea to extend MembershipUser class or to create separate class that has relationship (foreign key) with MembershipUser class UserID?
There is a thin line between what is considered to be Membership-related, and what is considered to be Profile-Related.
If the field you are referencing are not really membership/account specific, I would implement a different way of dealing with them other than the Membership Provider.
Solutions inlclude: The profile provider; Your own artifacts.