So far, I was successful in replacing the DNNSQLMembershipProvider with one that simply read from an XML file. It wasn't really functional, it was just a "proof of concept" sort of thing. It was based on the sample provider MS provides ("ReadOnlyXmlMembershipProvider") in the link I gave above.
So, that worked well enough, but all I did was replace the code in the class DNNSQLMembershipProvider. In other words, I didn't do it right.
Now what I want to do is create a separate class that will have my provider (which I'm going to call XmlMembershipProvider) and add that to my web.config, and use that. Here's what I added to web.config:
<add name="AbstractXMLMembershipProvider" type="DotNetNuke.Provider.AbstractXMLMembershipProvider"/>
That didn't work. What should I be doing here?
Incidentally, I'm still looking for some guidelines on writing a custom membership provider and plugging it in to DNN.
Also, the projected I added to the DotNetNuke.sln file produces it's output in a bin subdirectory in it's own project directory. All the other projects (e.g., the one for
DNNSQLMembershipProvider) appears to automatically have it's dll file copied to Website/bin, where it can be used by the website. How do I setup my new project to do this?
As you can probably tell I'm quite new to writing providers for DNN. Any help would be greatly apppreciated.
-Josh