Should I use the built-in membership provider for an ASP .NET MVC application?

Question

I\'ve been using a custom membership provider for authentication in all my web form applications till now. I\'m about to start developing my first website using MVC. I\'m

Answer 1

Take a look at what's happening with NerdDinner. They've recently (6 months ago) integrated with OpenID, with Google, Yahoo as featured providers. They're still allowing all their 'native' logins as well. Here's an example of a site allowing the user to authenticate in different ways.

If you can mirror some of their functionality, you'd be able to roll in Facebook, OpenAuth, etc. The big benefit is that it's already been implemented in ASP.NET MVC, and you'd just have to borrow some of that implementation.