DNN Ver: 5.6.7

I added a custom module to my site, and the View control works fine, but when I'm in edit mode and I select "Settings" I just get a Critical error "Object reference not set to an instance of an object."

I've verified that I have an actual settings.ascx file on my site and it's registered/installed according to the Host -> Extensions ->Edit Module Control screen.

Key: Settings
Title: MyModule Settings
Source: points to the correct file
Type: Edit

Is there another config that I haven't set? I've compared it to other modules that are working and everything looks the same.

Thanks

Thanks William, very helpful.

I was always checking the IIS Event Log - I didn't even know there was an Event Viewer page (*cough* noob). I now have the full error message AND a solution!  I verified that my Settings.ascx.cs file inherits from ModuleSettingsBase.

Error Message:
"DotNetNuke.MyModule.Settings' is not allowed here because it does not extend class 'System.Web.UI.UserControl'."

Solution:

Both the Settings.ascx.cs AND the Settings.ascx.designer.cs file need to inherit from the ModuleSettingsBase class. This is a new one to me, but adding the inheritance to the designer.cs file did the trick.

Thanks again!

Settings.ascx.designer.cs and Settings.ascx.cs should both define public partial classes of the same name (usually Settings) and must have the same namespace. Only the class defined in Settings.ascx.cs should inherit from DotNetNuke.Entities.SettingsModuleBase. In Settings.ascx the @Control directive should include an Inherits attribute with a value of the namespace qualified settings class.

I have found that sometimes Visual studio will incorrectly revert back to a base class (such as System.Web.UI.UserControl) when generating the designer file.