ModulesModule Class |
Namespace: CMS.Modules
public class ModulesModule : Module
The ModulesModule type exposes the following members.
Name | Description | |
---|---|---|
ModulesModule |
Default constructor
|
Name | Description | |
---|---|---|
AutoInitialize |
If true, the module is allowed to be initialized automatically
(Inherited from ModuleEntry.) | |
Initialized |
True if the module was initialized
(Inherited from ModuleEntry.) | |
IsDiscoverable |
If true, this module is automatically discoverable
(Inherited from ModuleEntry.) | |
IsInstallable |
Indicates if module is designed as installable.
(Inherited from ModuleEntry.) | |
ModuleInfo |
Gets the module info.
(Inherited from ModuleEntry.) | |
ModuleMetadata |
Gets the module metadata.
(Inherited from ModuleEntry.) | |
PreInitialized |
True if the module was pre-initialized
(Inherited from ModuleEntry.) |
Name | Description | |
---|---|---|
ClearHashtables |
Clears the module hashtables.
(Overrides ModuleClearHashtables(Boolean).) | |
GetObject |
Gets the object created from the given DataRow.
(Inherited from Module.) | |
CheckLicense |
Checks the license.
(Inherited from Module.) | |
Init |
Initializes the module.
(Inherited from ModuleEntry.) | |
OnInit |
Init module
(Overrides ModuleEntryOnInit.) | |
OnPreInit |
Handles the module pre-initialization.
(Inherited from ModuleEntry.) | |
PreInit |
Pre-initializes the module.
(Inherited from ModuleEntry.) | |
ProcessCommand |
Processes the specified command.
(Inherited from Module.) | |
RegisterCommand |
Registers the given command
(Inherited from Module.) | |
RegisterCommands |
Registers the object type of this module
(Inherited from Module.) | |
ResetUninstallationTokensOfInstallableModules | Cleans out uninstallation tokens for all modules, including associated data (i.e. module uninstallation files). This allows for module re-installation when the database has been lost, but the modules are still present in code base (e.g. after dropping the database and installing a new one using the wizard). This method must be called after application pre-initialization phase has finished (to reflect changes in custom path mapping). When called after the instance has already been initialized (and module installation processed), the module re-installation will occur upon next startup. |