I've been working on a an Active Directory Membership, Role and Profile provider so all the information is provided by Active Directory as apposed to SQL Server. I have everything working, but I've come across a very strange problem. On line 393 of the UserControler.vb it calls Microsoft.ScalableHosting.Profile.ProfileBase.Create(objUserInfo.Username, True) which returns objProfile which is a ProfileBase object. The objProfile is supposed to contain a series of properties that are named in the config file under the <profile> section.

When I debug to this point using the SQLProvider's specified in the MemberRole.dll the objProfile has the properties its supposed too, however for the life of me I cannot figure out why my providers break this. I've looked at the code for the MemberRole.dll (using reflector) to try and figure out what is going on. After much frustration of not being able to figure out what is wrong, I decompiled the entire MemberRole.dll into a project I called MemberRoleDbg, I changed the references of the DotNetNuke projects to point to the MemberRoleDbg, I changed the config file to use the it as well and DotNetNuke seemed to like it.

Now comes the very strange part, when I debug to line 394 (which is after the create) objProfile returns with 0 properties just like it would do with my provider, I double and triple checked to make sure it was loading the SQLProviders and it is.

I'm kind of at a loss as to where to go next I was hoping being able to decompile the dll and debug through it would show me what the SQLProvider was doing that I was not. I'm not sure who made the MemberRole.dll is there anyone I can contact to get more information or help from? or does someone have the original MemberRole.dll source that they could share?

-jeremy

PS this was orginally posted in the DotNetNuke forums, but was suggested I posted hear because the problem exists within the ProfileBase.

Did you ever find a resolution to your error?  Would you be willing to share the code for your membership Provider?

I did find a resolution, however I'd get in alot of trouble if I release the code (not sure why but someone else asked me and he said no) but I can help answer any questions you may have.

I am primarily interested in what files you needed to touch to pull username and profile information from the AD. 
I believe we want to just use DNN for security roles so as not to bog down the infrastructure guys everytime we need a new security role. 
I have .Net script to get a collection of user data from AD but would love some direction in what I actually need to edit to have DNN access the AD instead of the aspnet_users and aspnet_profiles tables.

Were you able to solve this?  I'm trying to add a custom implementation of ProfileBase.  To do this I created a custom ProfileConfigHandler to read the Inherits attribute.  When I set this equal to my custom ProfileBase class I get an exception in ProfileBase.InitializeStatic()

Exception Details: System.TypeLoadException: ?

Any ideas?

Thanks,
Brian Price