Strange installation

[leigh-pointer]

I have created and installed a module to my site and noticed that two records where created in the Modules table.

the database shows

on the server only 6 files installed:

is this correct?

[hishamco]

This is weird, seems the namespace is matter, hope to find time to validate this

[leigh-pointer]

@hishamco indeed very strange. Infact this is happening with another module that I have created.
Deleting the moduleDef "Controls" appears not to work but the record is removed and then added again.

[hishamco]

It may need a little investigation unless @sbwalker replied quickly ;)

[leigh-pointer]

Investigating further is appears that the extra ModDef that is being registered is the namespace to the folder with my razor components.

[leigh-pointer]

Ok fixed the issue if it is one?
All of my Razor components now inherit from ModuleControlBase this ensures Oqtane that they are part of the Module.

ModuleDefinitionRepository.cs (line 207)

// determine if this module implements IModule
Type moduletype = assembly
    .GetTypes()
    .Where(item => item.Namespace != null)
    .Where(item => item.Namespace == modulecontroltype.Namespace || item.Namespace.StartsWith(modulecontroltype.Namespace + "."))
    .FirstOrDefault(item => item.GetInterfaces().Contains(typeof(IModule)));
if (moduletype != null)
{
    // get property values from IModule
    var moduleobject = Activator.CreateInstance(moduletype) as IModule;
    moduledefinition = moduleobject.ModuleDefinition;
}
else
{
    // set default property values
    moduledefinition = new ModuleDefinition
    {
        Name = Utilities.GetTypeNameLastSegment(modulecontroltype.Namespace, 0),
        Description = "Manage " + Utilities.GetTypeNameLastSegment(modulecontroltype.Namespace, 0),
        Categories = ((qualifiedModuleType.StartsWith("Oqtane.Modules.Admin.")) ? "Admin" : "")
    };
}

because some of the conditions where not met part of the module is installed as a managed module.

[sbwalker]

This is by design. Modules must inherit from ModuleBase and be organized by namespace. You can either specify @namespace explicitly in your razor components... or Blazor will create a namespace for your components based on the folder structure and filename. Many different modules can exist in a single DLL. If you have razor components that you want to inherit from ModuleBase but not be treated as modules ( ie. shared components ) then you should use @Attribute [OqtaneIgnore] in your component. This is how all of the components in the /Controls folder are configured,.

[leigh-pointer]

Ok got it. Would it not, as a suggestion, update the description with a more rich description., especially from where it is found?

[leigh-pointer]

Applied the @attribute [OqtaneIgnore] to the razor files.