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.0Cannot Create Custom SQLDataProviderCannot Create Custom SQLDataProvider
Previous
 
Next
New Post
6/27/2007 2:48 PM
 

I thought it would something as easy as that, but I didn't want to assume.  :)  You have mail and thank you again!


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
6/27/2007 3:54 PM
 

The provider model in DNN assumes that any new provider will require every class that interacts with that provider to change.  Thus, when you create a new provider called PortalSqlDataProvider, it starts looking for classes that end in PortalSqlDataProvider instead of SqlDataProvider.  So... either replace/rename (just in the web.config) the core's SqlDataProvider, and use that name, or recompile all of the SqlDataProvider classes in the core as Whatever.PortalSqlDataProvider insead of Whatever.SqlDataProvider.

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
6/27/2007 4:56 PM
 

dukesb11 wrote

The provider model in DNN assumes that any new provider will require every class that interacts with that provider to change.  Thus, when you create a new provider called PortalSqlDataProvider, it starts looking for classes that end in PortalSqlDataProvider instead of SqlDataProvider.  So... either replace/rename (just in the web.config) the core's SqlDataProvider, and use that name, or recompile all of the SqlDataProvider classes in the core as Whatever.PortalSqlDataProvider insead of Whatever.SqlDataProvider.

Hope it helps,

Hmmm... I was about to be so "confused" and scratch my head some more.  At first when I made the suggested change, it still gave me the type error we have been going over.  Then, as I was about to give up and post to this thread again, I decided to reload the page one more time...

And it WORKS!  :)  Something had to clear in the application cache or something, I guess.  Thank you everyone for helping me with this.  And don't forget to follow the naming convention set forth by the DNN core.

What will continue to boggle me on this though is the need for the name to follow the pattern.  While tracing through this, I didn't notice anywhere in the code where it checks the classname or type name for "SqlDataProvider". 

Whew!  That was a tough one!  :)  Thanks again...


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Cannot Create Custom SQLDataProviderCannot Create Custom SQLDataProvider


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