Question

im building a new project in mvc 3 on MySql
i managed to make the membership work on MySql and use the login form that comes as default when creating a new mvc 3 application.
but…
i wanted to add more fields to the registration page like “sex” and “state”
i read that i should use the profilebase in order to do that.
but i had no luck with it..

my question is:
would you use the all membership provider for a small site?

or is it better to just implement Iprincipal on your own and create this kind of registration and login. with only one table in the database of “users”
so is membership provider out of the box is a bit overhead for a small project?

i didn’t find a good example for creating a basic registration form and login form in mvc 3
without the membership provider

would like to hear your opinion

thanks!

Answer 1

Here are some answers which might help you decide.

1. Should I use the built-in membership provider for an ASP .NET MVC application?
2. How do you get the UserID of a User object in ASP.Net MVC?
3. How to create a asp.net membership provider hashed password manually?

UPDATE

An example for creating a custom registration and login? Possibly. Here’s an example of creating a custom Provider and Identity … and using Facebook to handle the username/password credentials. Even though this project uses RavenDb as the database, it’s a 1 second job to swap that out and use EF/L2S/NHibernate, etc… or even a normal forms auth where you ask for a username / password.