Hello

I was following Philip Beadle's blogs for TDD for DNN modules. I have started to add similar approach in one of my existing module.

My module usage DAL+. I have not created my own separate SqlDataProvider, instead I am using DotNetNuke.Data.DataProvider.Instance().ExecuteNonQuery() and other generic methods.

When I started my tests in MBUnit I was getting Null object exceptions from "DotNetNuke.Data.DataProvider.Instance()".

I did some digging and found, that following line was not able to create object.

    objType = BuildManager.GetType(TypeName, True, True)

(DNN 4.8.1, \Library\Components\Framework\Reflection.vb Line#:278)

But why is that so - its working while I use site in browser. And thats where I found answer - BuildManager is "Provides a set of methods to help manage the compilation of an ASP.NET application.". So that means its work fine in ASP.NET running environment but not when you are using it in MBUnit thread.

Finally what I found is there was no AssemblyName passed in "TypeName" parameter for "BuildManager.GetType()" so it try to find that class in all loaded assemblies (in current thread domain). And no way "DotNetNuke.SqlDataProvider" will be loaded my MBUnit.

To resolve this issue, I just update a single line in DNN DataProvider class.

From:         Private Const ProviderAssemblyName As String = ""

To:               Private Const ProviderAssemblyName As String = "DotNetNuke"

(DNN 4.8.1, \Library\Components\Providers\Data\DataProvider.vb Line#:32)


This change works fine in both ASP.NET and MBUnit environment. I will really appreciate if this tiny update can make in to DNN core.