Is there any way in the module manifest to remove a control? I've been through: http://www.dotnetnuke.com/Resources/W... - and I know I can add/remove items from the web.config - but what about the Module controls themselves?

---

---

Andrew Walker

If you enjoy making your own beer and/or wine - be sure to check out http://www.ForemostBrewing.com

Thanks for the reply Robert!

That will remove the file - but I don't think it's gonna remove the  module control itself.  I may need to expand a little more.

Let's say I have a module and one of my module controls is setup as:
Control: Categories  (to access via Globals.NavigateUrl(TabId, "Categories");)
Source: DesktopModules/MyCompany/MyModule/Categories.ascx

Now - as my module grows and simplifies - I no longer need the Categories module control.  Running the cleanup should remove the ascx file itself - but I still have the entry for the control "Categories" under Module Controls.

I just don't want to have to go in to the Module itself and delete the Module Control from the definition - as this module is used on many dnn installs.

---

---

Andrew Walker

If you enjoy making your own beer and/or wine - be sure to check out http://www.ForemostBrewing.com

Andrew,

This is best handled in a module's implemention of the IUpgradable interface as there is currently no capability in the manifest file to remove or better stated to "unregister" a module control. Here's a link to the DotNetNuke Wiki for IUpgradable: http://www.dotnetnuke.com/Resources/W...

I recall that several admin modules included in the DotNetNuke framework had to remove or rename one or more of their module controls either during the upgrade from 4.x to 5.x but can't recall which ones. Another module which may have removed a control during its upgrade is Form and LIst. You might take a look at their source code to see how it was done.

Basically in your implementation of IUpgradable you would do something like the following given that you know the desktopModuleName and the control's controlKey:

publlic void RemoveModuleControl (string desktopModuleName, string controlKey)
{
    // get desktop module from DesktopModuleName
    var dmi = DesktopModuleController.GetDesktopModuleByModuleName(desktopModuleName, -1);
    if (dmi != null)
    {
      // get module definition
     var mdi = ModuleDefinitionController.GetModuleDefinitionByFriendlyName(moduleDefinitionName, dmi.DesktopModuleID);
      if (mdi != null)
      {
         // get Module Control
         var mc = ModuleControlController.GetModuleControlByControlKey(controlKey, mdi.moduleDefId);
         if (mc != null)
         {
          ModuleControlController.DeleteModuleControl(mc.ModuleControlID);
          }
       }
    }
}

Please note that I have not tested the above code and that you may want to log or otherwise handle the various potential errors should the DesktopModule, the ModuleDefinition or the ModuleControl not exist.

---

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