Custom Membership Provider - Implementation Question

Hi all,

I started implementing a Custom Membership Provider that would keep all membership data in one table, would have only one user class and also would have the data layer managed by an ORM (Telerik ORM) for easy porting from one project to another. I researched this topic and found a couple of sample implementations but it seems that instead of having one class to hold all membership data there is always the System.Web.Security.MembershipUser and another class that inherits from it(not always but you still get two classes), and there is a bunch of casting and instatiating new objects and moving data from one to another involved.

Now is there a way to have a Custom Membership Provider without having to have two classes and keep exchanging data between the both ? I think the approach of having to inherit classes is not as good as having to implement an interface, for some reason i think if MS would have provided an interface to be implemented using two classes would have not been necessary.

What do you guys think ? Any help is greatly appreciated !

Re: Custom Membership Provider - Implementation Question

You can simply inhert Membership class and can write your custom BLL class call to validate employee logins. See below example for an idea about how it will work.

Public Class LiveMembershipProvider
Inherits MembershipProvider

Public AccountEmployeeBLL As AccountEmployeeBLL

        Public Overrides Function ValidateUser(ByVal username As String, ByVal password As String) As Boolean
            Return Me.AccountEmployeeBLL.ValidateLogin(username, password)
        End Function