Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0New Membership Provider ProblemNew Membership Provider Problem
Previous
 
Next
New Post
5/24/2007 10:47 AM
 

Ok, I found the issue. After I was able to debug through the application by setting a breakpoint at the application_start of the global.vb and stepping through all the code I saw the type of the membership provider specified on the web.config was mispelled. I corrected the spelling and I now have a new membership provider.

Thanks for all the help and the inspiration...

 
New Post
5/24/2007 11:01 AM
 

So the default provider (ASPNetMembership) loads fine but yours does not. If you have the DotNetNuke.dll source code available set a breakpoint on the Reflection.CreateObject(...) method so that you can see what the values are of AssemblyName and ClassName are. You will probably find that this are not correct.

Hope this helps,

hk

 


Henry Kenuam
Engage Software
St. Louis, MO
314.966.4000



The leading provider of DotNetNuke support, training and custom module development
 
New Post
5/25/2007 1:30 AM
 

Is it possible to get the code for your provider, minus your internal connectivity stuff? I am looking at building my own provider as well but can't seem to get the basic implemented the right way.

My email is brian at onehumanfamily dot com.

Thanks,

Brian

 
New Post
5/25/2007 11:41 AM
 

OHFInc wrote

Is it possible to get the code for your provider, minus your internal connectivity stuff?

Bryan,

    As I mentioned before, all i did was create a new project and I inherit from the default provider (the DNN Asp Net membership provider). Since I need to keep 2 DBs in synched all i do is override the create and update methods of the provider, call the base and then update the other DB. Very simple.

  What you could do is use the current provider as a template for your new one and change whatever doesn't apply to you.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0New Membership Provider ProblemNew Membership Provider Problem


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out