you should replace the string "company" with your own (virtual) company's name to avoid possible naming conflicts with other developers!

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Thanks for the clarification on root namespace... sometimes I get a little confused going from c#.net to vb.net. Now I am getting a DataProvider error in my project. The variable Dataprovider is ambiguous with DotnetNuke.Data and mine is at Company.Modules.StudentInformation namespace in the abstract class DataProvider. I have a SQLDataprovider that inherits DataProvider but will not work... it is a name collision. I have tried fully qualifying my DataProvider by Company.Modules.StudentInformation.DataProvider.Instance() but then I get the error:

ex.Message() "The type initializer for 'Bla.Modules.MyModule.DataProvider' threw an exception." String
+ InnerException {"Value cannot be null.
Parameter name: type"} System.Exception

I've researched this for a while and most say it is a web.config setting or a namespace situation but I cannot seem to figure it out.

I am using a wap project... am I missing some reference to a dotnetnuke dll? I tried adding a reference to DotNetNuke.SQLDataProvider.dll in my asp.net project but it is still erroring.

The custom module compiles, installs fine, works rendering pages and so forth, but it errors every time it goes to use my custom sqlDataprovider to hit the db.

I know this is a common error, the data provider ambiguous name, but what else can I look for to fix this up so my custom sql data provider will work? What steps should I review to see what I am missing?

Most people do not have to fully qualify their inherits statement for inheriting DataProvider in the SQLDataProvider class but I even tried fully qualifying it and the ambiguous error ws was still present!

I.E...

Public Class SQLDataProvider()
Inherits Company.Modules.StudentInformation.DataProvider

What am I missing?

Thanks for any help!