1

For a project I am currently working on, I am interested in allowing users to provide multiple e-mail addresses, both for contact purposes as well as providing address book-based social matching. I plan to write a custom membership provider (aspnet_Membership table is too heavy for my liking), but the MembershipProvider system only allows for one e-mail address per account.

What would be the best idea for using the membership provider system but allow for multiple e-mail addresses per user? Or should I avoid MembershipProvider completely and roll my own system?

GEOCHET
  • 21,119
  • 15
  • 74
  • 98
Chris Charabaruk
  • 4,367
  • 2
  • 30
  • 57

1 Answers1

3

You can certainly do this. In addition to writing a custom MembershipProvider class, you will need to create a derived class from MembershipUser to hold the additional e-mail address fields. Instructions on how to do this are available here.

Matt Peterson
  • 5,169
  • 4
  • 32
  • 34