I wrote my own customer membership implemention for a project in ASP.Net. I now wish to bring this project in to MVC4. Now, should I just concert my userdb to simplemembership OR implement my membership provider? It's very simple. Just a one table job.
I can't quite work out how to use my provider in MVC4. I know I have to change it to ExtendedMembershipProvider. What do I need to add to the web.config? Will [authorize] and all that still work with my provider?
If not, I'm probably better to convert it to SimpleMembership. If this is the case, what's the best way to go about this?
Sorry the question is kind of all over the place.
If this post helped you solve your issue, please mark it as answered.
If you plan to use your Membership Implementation then you can still use it in MVC4 but you will not be able to use the newlly Added APIs.
Question is do you really want to convert or migrate to new APIs if yes, then SimpleMembership is a good choice as it has abstract implementation and you can plug in any database or table structure you want
I wrote my own customer membership implemention for a project in ASP.Net. I now wish to bring this project in to MVC4. Now, should I just concert my userdb to simplemembership OR implement my membership provider? It's very simple. Just a one table job.
What benefit is membership giving you? What other parts of the framework are you using that saves you time?
infused
Member
107 Points
61 Posts
asp.net -> mvc4 membership
Jan 19, 2013 08:25 AM|LINK
Hi Guys,
I wrote my own customer membership implemention for a project in ASP.Net. I now wish to bring this project in to MVC4. Now, should I just concert my userdb to simplemembership OR implement my membership provider? It's very simple. Just a one table job.
I can't quite work out how to use my provider in MVC4. I know I have to change it to ExtendedMembershipProvider. What do I need to add to the web.config? Will [authorize] and all that still work with my provider?
If not, I'm probably better to convert it to SimpleMembership. If this is the case, what's the best way to go about this?
Sorry the question is kind of all over the place.
CPrakash82
All-Star
18286 Points
2842 Posts
Re: asp.net -> mvc4 membership
Jan 19, 2013 06:16 PM|LINK
If you plan to use your Membership Implementation then you can still use it in MVC4 but you will not be able to use the newlly Added APIs.
Question is do you really want to convert or migrate to new APIs if yes, then SimpleMembership is a good choice as it has abstract implementation and you can plug in any database or table structure you want
See here.
BrockAllen
All-Star
27534 Points
4907 Posts
MVP
Re: asp.net -> mvc4 membership
Jan 20, 2013 01:01 AM|LINK
What benefit is membership giving you? What other parts of the framework are you using that saves you time?
http://brockallen.com/2012/06/04/membership-is-not-the-same-as-forms-authentication/
http://brockallen.com/2012/09/02/think-twice-about-using-membershipprovider-and-simplemembership/
DevelopMentor | http://www.develop.com
thinktecture | http://www.thinktecture.com/