2

I've been reading about overriding the Membership Provider and the Role Provider. I think this is what you need to do when doing Asp.net Form projects. Is this also the way to go with Asp.net MVC projects or there is a better way to do so?

Thanks :)

Joe Phillips
  • 49,743
  • 32
  • 103
  • 159
Roman
  • 10,309
  • 17
  • 66
  • 101
  • So what exactly is your question? How to implement a custom provider? When should you implement a custom provider? Are there practical differences in usage of providers when using MVC as opposed to WebForms? I really can't tell. Here's a tip: One clear question, One clear answer, lots of happy people. – Sky Sanders May 09 '10 at 12:50

2 Answers2

0

Yes, ASP.NET MVC uses the Membership API by default. However, you can always use your own logic if you want to, but most functionality for the Membership API is in there already.

You'll need:

  • A custom MembershipProvider
  • If you use roles, a custom RoleProvider
  • If you use profiles, a custom ProfileProvider
Venemo
  • 18,515
  • 13
  • 84
  • 125