Here's my idea; I want to build a module that is split into a handful of custom controls. The module will consist of a dropdown to select which control to view. These controls need access to the DNN framework (portal info, user info, role info, etc) but separate from the module definition. They will be in the same VS project and compiled into the same DLL however. A few questions came up while concocting this plan;

• Is this possible?
• Do I still need to inherit PortalModuleBase?
• Can I just drop the control into the main module page like I would a normal custom control?

Any help would be appreciated. Plan B is to put everything into one module and split the would-be-custom-controls into ASP.NET panels to control visibility. Plan B is not ideal though as the project would become hard to manage pretty quick.

Thanks.

So each control that I would drop in the main module control would be written as a module control itself? And just not included in the module definition?

I would agree with Chris on this one.  I am personally moving to this for some of my projects and I like the way it is working thus far.