Custom Providers & Design Patterns

Posted by Code Sherpa on Stack Overflow See other posts from Stack Overflow or by Code Sherpa
Published on 2010-03-24T18:57:43Z Indexed on 2010/03/24 20:03 UTC
Read the original article Hit count: 330

Hi.

I am using ASP.NET 2.0 and its various providers. I have overridden most of the methods I need and have the following custom providers:

ProjectMembershipProvider ProjectProfileProvider ProjectRoleProvider

In the design of my project, my intention was to wrap the custom providers in a facade - style design - mixing and matching profiling, membership, and roles in API methods to simplify things for developers.

But, I am finding that a lot of the methods in my custom providers don't need to change, really. And, it seems silly to wrap a stand-alone method in another method that does exactly the same thing.

So - is my approach wrong? Or, should I allow end - users to instantiate the custom providers when needed and the mix/match api when needed? This seems a bit redundant to me but I can't see another way.

Advice appreciated.

Thanks.

© Stack Overflow or respective owner

Related posts about c#

Related posts about asp.net-membership