There is a bug in mono linker where the assembly is added even if its getting removed by the compiler.

This breaks the lazy loading since assemblies are now added to the boot sequence.
Disabling the linker fixes the issue, which I guess its ok.

Author: isc30

demo/WasmHost/LinkerConfig.xml renamed to demo/ServerHost/LinkerConfig.xml

@@ -2,8 +2,13 @@
 
     <PropertyGroup>
         <TargetFramework>netcoreapp3.1</TargetFramework>
+        <BlazorWebAssemblyEnableLinking>false</BlazorWebAssemblyEnableLinking>
     </PropertyGroup>
 
+    <ItemGroup>
+        <BlazorLinkerDescriptor Include="LinkerConfig.xml" />
+    </ItemGroup>
+
     <Import Project="../BlazorLazyLoading.Server.props" />
 
     <!-- Extra dependencies -->

demo/ServerHost/ServerHost.csproj

@@ -3,14 +3,15 @@
     <PropertyGroup>
         <TargetFramework>netstandard2.1</TargetFramework>
         <RazorLangVersion>3.0</RazorLangVersion>
-        <BlazorWebAssemblyEnableLinking>true</BlazorWebAssemblyEnableLinking>
+        <BlazorWebAssemblyEnableLinking>false</BlazorWebAssemblyEnableLinking>
     </PropertyGroup>
 
     <ItemGroup>
         <BlazorLinkerDescriptor Include="LinkerConfig.xml" />
     </ItemGroup>
 
     <Import Project="../BlazorLazyLoading.Wasm.props" />
+    <Import Project="../BlazorLazyLoading.Components.props" />
 
     <!-- Extra dependencies -->
     <ItemGroup>
@@ -22,8 +23,8 @@
 
     <!-- Modules -->
     <ItemGroup>
-      <ProjectReference Include="..\Core\Core.csproj" />
-      <ProjectReference Include="..\ModulesHost\ModulesHost.csproj" />
+        <ProjectReference Include="..\Core\Core.csproj" />
+        <ProjectReference Include="..\ModulesHost\ModulesHost.csproj" Private="false" />
     </ItemGroup>
 
 </Project>