c# - Provider Design Patterns in asp.net -

i need dll architecture / design patterns / oo.

i have been learning class factory design patterns solution current challenge , use feedback @ point.

i have 3 classes custom wrappers asp.net 2.0's profileprovider, membershipprovider, , roleprovider.

i'd implement way of calling each reasonably simple , intuitive developers. effect of:

object obj = new users().permissions.createrole(); object obj = = new users().membership.createuser(); object obj = = new users().profile.getuserprofile(); 

the examples have read on how using abstract class factory (if, indeed, way go) confusing (i have been working way round this link ).

any suggestions on best practices how started? or, better, code illustrations? :)

the apis membership provider classes pretty straightforward , don't think there's gained wrapping them. think you're looking facade pattern. create class encapsulates user management activities application , hides internal implementation. calls class might like:

userservice.createadminuser("keith", "godchaux"); 

the userservice class use membership provider create new user , assign admin role them.