ASP.NET MVC2 and MemberShipProvider: How well do they go together?

Posted by Sparhawk on Stack Overflow See other posts from Stack Overflow or by Sparhawk
Published on 2010-06-17T20:14:46Z Indexed on 2010/06/17 21:03 UTC
Read the original article Hit count: 630

I have an existing ASP.NET application with lots of users and a large database. Now I want to have it in MVC 2. I do not want to migrate, I do it more or less from scratch. The database I want to keep and not touch too much.

I already have my database tables and I also want to keep my LINQ to SQL-Layer. I didn't use a MembershipProvider in my current implementation (in ASP.NET 1.0 that wasn't strongly supported).

So, either I write my own Membershipprovider to meet the needs of my database and app or I don't use the membershipprovider at all.

I'd like to understand the consequences if I don't use the membership provider. What is linked to that? I understand that in ASP.NET the Login-Controls are linked to the provider. The AccountModel which is automatically generated with MVC2 could easily be changed to support my existing logic.

What happens when a user is identified by a an AuthCookie? Does MVC use the MembershipProvider then?

Am I overlooking something? I have the same questions regarding RoleProvider.

Input is greatly appreciated.

© Stack Overflow or respective owner

Related posts about asp.net-mvc

Related posts about forms-authentication