Hello All,

I am trying to find out which is the preferred way of logically and physically packaging and deploying my controls within a module definition.

My current UserProfile module has 6 .ascx files (controls in it). Currently when I package it, I have them all under one folder in the .DNN file. This means there is one entry in the Module List and one module to select from. When I add it to a page I get all 6 controls and I have to tell user's how to move them etc (confusing to some).

I noticed other complex modules break up their modules into multiple folders by partiitioning their .DNN files. This means you get multiple entries in the drop down list so it's easier to install and manage the module. BUT I also noticed that they are treated atomically, so if you uninstall one then it does not affect the others, and the directory it was in still remains.

I am trying to work out what the core PA uninstaller expects, because it looks to me like partitioning your module in this manner means it won't completely uninstall (ie. it leaves folders). This means it would not pass the DNN Module Certification program. Is the module configuration wrong? Is the DNN PA Core installer limited? What should I do today when I package my modules? I know this area is being refined, but I don't want to make the wrong choice now.

PS. I raised this on Scott McCulloch's site as I noticed his (brilliant) News Article module uses the split approach, and it also does not uninstall completely. You can read it here.

Opinions please...

---

Thanks,
Rodney
Smart-Thinker - Home of SmartSocial - the 100% Free DotNetNuke Social Networking Product Suite
Do use DNN a lot? Try the DotNetNuke Toolbar to save you time!
PokerDIY - Example Implementation of DNN Social Network

---

Thanks,
Rodney
Smart-Thinker - Home of SmartSocial - the 100% Free DotNetNuke Social Networking Product Suite
Do use DNN a lot? Try the DotNetNuke Toolbar to save you time!
PokerDIY - Example Implementation of DNN Social Network