Fixed issue in client-side Blazor, added ModuleMessage to ModuleInstance

Oqtane.Client/Shared/ModuleInstance.razor

@@ -1,6 +1,9 @@
 @namespace Oqtane.Shared
 
-@DynamicComponent
+<CascadingValue Value="this">
+    <ModuleMessage @ref="modulemessage" />
+    @DynamicComponent
+</CascadingValue>
 
 @code {
     [CascadingParameter]
@@ -9,6 +12,8 @@
     [CascadingParameter]
     private Module ModuleState { get; set; }
 
+    private ModuleMessage modulemessage { get; set; }
+
     RenderFragment DynamicComponent { get; set; }
 
     protected override void OnParametersSet()
@@ -32,11 +37,14 @@
             }
             else
             {
-            // module does not exist with typename specified
-            builder.OpenComponent(0, Type.GetType(Constants.ModuleMessageControl));
-                builder.AddAttribute(1, "Message", "Error Loading Component For Module " + ModuleState.ModuleDefinitionName);
-                builder.CloseComponent();
+                // module does not exist with typename specified
+                modulemessage.SetModuleMessage("Error Loading Component For Module " + ModuleState.ModuleDefinitionName, MessageType.Error);
             }
         };
     }
+
+    public void AddModuleMessage(string message, MessageType type)
+    {
+        modulemessage.SetModuleMessage(message, type);
+    }
 }