Hi,

I'm new to dotnetnuke, and want to write my own membership provider. I have a couple of questions related to this:

1) As a starting point I copied the source from Provider.Membership.AspNetProvider to a new project, including this project in a solution with my DNN website, and switching the website's Provider.Membership.AspNetProvider reference from binary to the new project. When I start the site and login, I hit my breakpoint in the UserLogin method, and all works OK. I then added a new project to my solution, again copying the Provider.Membership.AspNetProvider source. This time I changed the namespace to aa.bb.cc.Security.DNN, and the classname to MembershipProvider. I added this line to the Membership Providers section of web.config:

add name="MyMembershipProvider" type="aa.bb.cc.Security.DNN.MembershipProvider, aa.bb.cc.DNN.Provider" providerPath="~"

Now when I run up the site, I get an "Provider must implement the class 'System.Web.Security.MembershipProvider'" exception (this is with switching the default provider to MyMembershipProvider.

Can anyone tell me where I'm going wrong? Both Provider.Membership.AspNetProvider and aa.bb.cc.Security.DNN.MembershipProvider inherit from DotNetNuke.Security.Membership.MembershipProvider ??

2) A more general question - it seems from what I've read that my new provider must keep the DNN user and role tables (both the core DNN tables and aspnet_ tables) in sync with my external membership tables. Is this purely because some of the DNN modules hit these tables directly? If so, is it safe to sync just a subset of the data (ie exclude passwords, email addresses etc)

Many thanks!

Pete