Author: hard_life | Posted on: 10/9/2009 2:05:59 AM | Views : 285

I'm in the beginning phase of building a new web-application. Unfortunately, I'm stuck having to build this application on top of a database, that I cannot alter in any way, as a number of legacy apps will be running against it for quite a while.
Being fairly new to ASP.NET, I considered just rolling my own membership functionality, but doing a bit of research, it seems I could get a fair bit out-of-the-box functionality creating membership and roleprovider implementations - enabling me to use the controls in the framework.
My problem is, that the database is constructed in a way, so that there is really no specific role information table. Instead there are 3 different tables, each representing the 3 different kinds of member entities there are. The old application that I'm replacing, just attempts to log in by looking in each of these tables one by one, ultimately picking a member type if there is a match in the corresponding table.
My question, for so ...

Go to the complete details ...