Here's a little background on my business requirements. We have a Microsoft CRM Solution for internal purposses and an installation of DNN 4.X for our public website. The business need is to have the users on DNN in synched with the contacts on CRM. So for every new user on DNN I have to create a new contact on CRM and for every user upgrade on DNN I have to upgrade the contact on CRM. The same thing goes the other way around. The good news is I have already implemented this solution and it works. I use an API that I created which updates CRM. The bad news is that the code lies on the code behind of the website, so with every upgrade of DNN, the code gets overwritten. This time I decided to take it one step further and create a new Membership Provider.

I don't need anything new other than calling my API when the user is updated or created so I decided to create a new project with a class that inherits from the already created DotNetNuke.Security.Membership.AspNetMembershipProvider. My provider then overrides 2 methods. Here's the code:

  DotNetNuke.Security.Membership
  Public Class IPPEAspNetProvider
    Inherits DotNetNuke.Security.Membership.AspNetMembershipProvider

    Dim MyCrm As New CRM()

    Public Overrides Function CreateUser(ByRef user As DotNetNuke.Entities.Users.UserInfo) As DotNetNuke.Security.Membership.UserCreateStatus
      Dim ret As DotNetNuke.Security.Membership.UserCreateStatus = MyBase.CreateUser(user)
      IppeCrm.User = user
      IppeCrm.CreateContact()
      Return ret
    End Function

Namespace

jstawski,

The actual error (which isn't all that helpful) occurred in DotNetNuke.Security.Membership.MembershipProvider.Instance(). The first thing you will want to do is open your DNN solution and add the DotNetNuke (.dll) source project to your solution, remove the .dll reference and re-add the DotNetNuke (.dll) project reference. This way, you can set a breakpoint on DotNetNuke.Framework.Reflection.CreateObject(). Since this mechanism is used for loading all sorts of "provider" type classes you will see this run fairly often. This will allow you to narrow down who is calling this method with bad parameters. Most likely this will be a .config file problem or the dll containing the class isn't in the probing path for .NET.

Hope this helps,

Regards,

hk

Here are more findings. To make sure the issue was not related to an inheritance problem. I modified my code. I copied the entire code from AspNetMembershipProvider and paste it into my new provider. I made sure the references are all the same in both projects and just in case of some reflection thing, I copied the assemblyinfo.vb content into the new assemblyinfo.vb (I left the original guid.)  I compiled with no problems, added the dll into the dnn web project and I still get the same error. That rules out a problem with the membership provider and it means we should focus on the configuration side.

Any ideas?