Greetings all, I don't know if this is by design or what but I discovered today that DNN 5.0 is short one overload of the "ProcessModuleLoadException" method when compared to previous versions. I found this out when testing some modules we developed in a clean install of DNN 5.0.0.
The installation of the module (legacy package format) went without a problem and I was able to place the module on a page. However when I tried to add a record I got the following error...
Method not found: 'Void
DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(System.String,
DotNetNuke.Entities.Modules.PortalModuleBase, System.Exception, Boolean)'.
I did some digging using VS Object Browser and found the following. The overload highlighted in red does not exist in 5.0.0.
The following are the ProcessModuleLoadException methods in the 4.9.1 version of the DotNetNuke.Services.Exceptions.Exceptions class:
ProcessModuleLoadException(String, Control, Exception)
ProcessModuleLoadException(String, Control, Exception, Boolean)
ProcessModuleLoadException(String, PortalModuleBase, Exception, Boolean)
ProcessModuleLoadException(Control, Exception)
ProcessModuleLoadException(Control, Exception, Boolean)
ProcessModuleLoadException(PortalModuleBase, Exception)
ProcessModuleLoadException(PortalModuleBase, Exception, Boolean)
Below are the ProcessModuleLoadException methods in the 5.0.0 version of the DotNetNuke.Services.Exceptions.Exceptions class:
ProcessModuleLoadException(String, Control, Exception)
ProcessModuleLoadException(String, Control, Exception, Boolean)
ProcessModuleLoadException(Control, Exception)
ProcessModuleLoadException(Control, Exception, Boolean)
ProcessModuleLoadException(PortalModuleBase, Exception)
ProcessModuleLoadException(PortalModuleBase, Exception, Boolean)
I don't know why we used this particular overload but thought it was interesting that this was not depreciated as opposed to being removed. Then I thought it may be an oversight. Does anyone know if this is an oversight or by design?