We have looked at using the SqlMembershipProvider but we need to to be able to authenticate the users with a pin and a password, does this mean we have to provide custom implementations of MembershipProvider and RoleProvider? It seems impossible to use the SqlMembershipProvider because we would be changing the schema of the database, and we would have to write our own login controls...
This in mind, Why shouldnt we just create your own schema an user model from scratch? What are the actual benefits of using RoleProvider and MembershipProvider and writing custom sql commands to connect these to a databse?
Seems like a good idea to use these classes but not sure what advantage exactly they give us apart from login controls being bound to then and therefor being easier to implement,
Any help much appreciated...
Regards,
Peter Go to the complete details ...