Hi all
We have an existing ASP .Net web application which uses the MS membership provider model. Currently, we are using the sample SqlTableProfileProvider profile provider http://www.asp.net/downloads/sandbox/table-profile-provider-samples/.
We are doing an extensive redevelopment of the application, including a much more layered architecture with a distinct layer encapsulating all domain logic. The data access logic has become more complex, as "profile" (RegisteredUser in domain parlance) data is now aggregated from several different tables in our database. Data persistence now involves referencing web services and calling web methods; in addition to writing directly to the database. Consequently, the existing profile provider is no longer appropriate.
What I want to do with as little work as possible is to keep the existing membership and profile system in place, but write custom provider[s] that talk to the domain layer instead of dealing with simple database queries. This doesn't feel as if it should be too difficult (famous last words) given the clear and cohesive domain API that I have to deal with, but I'm having problems finding articles or examples - everything seems to be geared towards direct database access of one sort or another when implementing custom profile providers.
Does anyone have any advice, comments, or references to good resources with which I can educate myself on this subject? Amy assistance at all would be very gratefully received.
Cheers!
Chris Marsh