Support Components from NuGet packages

[isc30]

Mentioned in #42

• Check if referencing the package generates the metadata properly
• (possibly) Check if adding the assembly to BLLManifestGeneratorAssemblyNames works
• Document the solution

[isc30]

Assemblies from PackageReferences should be added too .targets file where this happens

[isc30]

Just checked a fast approach for this and im able to lazy load MatBlazor easily :)

[FrMalan]

Awesome work dude! I just started playing with this for an internal project that will need to load UI modules on demand. So far for my POC phase it seems to work very good for the moment.

[isc30]

After some investigation, I'm planning to rework the manifest system a bit so I open the posibility of people implementing their own ManifestGenerators.

Loading NuGet packages works completely fine, and generating the lazy manifest for them too (by adding them to BLLManifestGeneratorAssemblyNames.

I want to implement nested Module discovery by stamping the assemblies with a custom attribute so I can join the manifests on build time on the top-most Module. This way, your project referencing the nuget package could include the BLLManifestGeneratorAssemblyNames bit itself but the parent will be aware of it too (there is no easy way of inheriting msbuild props).

Also, for modules requiring static assets (like a JS being appended to the page etc) I will need to implement #9 first.

I just created a PR (#48) with a Module that depends on Faso.Blazor.SpinKit.SpinKitWave and uses it directly and lazily.

As for the rest, #47 will do.

[isc30]

Closing the issue since it was splitted.

• AssemblyInitializer (Startup) #9
• Rework the Module system #47