2

I was wondering, what's the best approach in creating users authentication for my asp.net-mvc web application.

Should I use the Forms authentication using a custom MembershipProvider ? Or should I implement my own login and registration mechanism for my users?

2 Answers 2

3

Seems silly to reinvent the wheel if you don't have a pressing business need to do so. I'd go with forms authentication with a custom provider (if necessary)

Sign up to request clarification or add additional context in comments.

Comments

0

Unless you have some special needs, its always best to use the out-of-the-box solution. So perhaps you should describe what considerations makes you consider rolling your own? (And add that information to the original question - this will help people provide useful answers).

3 Comments

I just don't like the idea of infecting my DB with those asp.net tables and stored procedures. :-)
The problem is, I want to store extra data for the users and I don't want to use join on my queries - with the asp.net user table and the userdata table.
Every membership user has a GUID, just add that to the userdata table. no relationship needed.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.