Hello everybody,

i have one very annoying exception when I try to use module, developed separatelly from DotNetNuke project and then packed and installed in DotNetNuke from PA. The exception looks like that: Unable to cast object of type 'DotNetNuke.Modules.xx.SqlDataProvider' to type 'DotNetNuke.Modules.xx.DataProvider' (DotNetNuke.Modules.xx is the namespace).
The exception occures here:
objProvider = ((DataProvider)(Framework.Reflection.CreateObject("data", "DotNetNuke.Modules.xx", "")));

in DotNetNuke.Modules.xx.DataProvider class in static CreateProvider() method.

The DotNetNuke.Modules.xx.SqlDataProvider really extends from DotNetNuke.Modules.xx.DataProvider so I'm confused here. It's certainly is ASP issue, but still, maybe someone have met such thing before, so I would appreciate any help..

Kvietinis

Hello, Brandon,

i've allready looked what the type of an object, that CreateObject contructs, but I didn't looked what the BaseType of an object. Thanks, for the starting point.

Ignas

Hi Ignas,

I'm afraid that I don't have too many additional ideas to offer.  Clearly there is some sort of strange typing problem going on. 

Have you tried searching the VS object browser for "DataProvider" and checking to make sure that there isn't a ghost object out there that isn't involved in your inheritance chain?  I've accidently misnamed a partial class before that caused problems like this.

I'd also change your (DataProvider) cast to be more explicit (DotNetNuke.Modules.xx.DataProvider), and I'd probably also play around with the debugging code a bit more to see if I could figure out why VS thinks that SqlDataProvider does not inherit from DataProvider.  Perhaps, in the same code file, create a temporary class that inherits from DataProvider.  Instantiate that class and check that its BaseType is equal to SqlDataProvider's BaseType.

Finally, is there an inner exception or any additional debugging information about the cast error?

Brandon