The idea is to mix two providers, and by default, that's not allowed (either the first, or the defaultProvider will be initialized). So we created MixedMembershipProvider that aggregates two other providers, the default DotNetNuke's AspNetMembershipProvider and our own. Depending on user action, the mixed one decides automatically what to choose based on a variant of Strategy and Facade.
The providers of DNN do not inherit from ASP.NETs providers, and the documentation is almost non-existent. The question is, can I use the AspNetMembershipProvider standalone, should I do some initialization magic or is there anything else I should think of?
This works:
this._dnnMembershipProvider = new AspNetMembershipProvider();
but the code has some issues (can't find some users, but can't add them either, duplicate username error) and I just like to know whether this part is correct at least (i.e. ASP.NET's default MembershipProvider needs to be properly initialized before you can use it).