The Blog module is one of only a few DNN modules which make use of multiple module definitions. When registering your current module implementation in the DNN database (Host --> Module Definitions --> Create Module Definition), you may have noticed that after creating the definition, a Definitions drop-down list appeared and below it a New Definition textbox and "Add Definition" link button appeared. This is where you would need to add a second definition and its related module controls. When a module with more than one definition is added to a page, it will appear as multiple (but related modules). Multiple module definitions may also be set up in the .dnn manifest file for the module.

Regarding your question about VS intellesense not seeing other controls of the module, I'm not sure what your asking as two module controls (which are really .ascx UserControls) would not normally "see" each others properties and methods even when in the same physical folder or namespace.

I would suggest that you take a close look at the structure of the user control files and the .dnn manifest of the Blog module for pointers on how your own multiple definition module should be set up. Another module which uses this approach is my own ePrayer module available for free (including source code) on my website. The DNN Blog module uses the compiled (WAP) approach to development while my uses the dynamic-compilation (WSP) model.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner