Blazor bundling and resources

[TimoSalomaki]

The Built-In Themes article mentions that the way Blazor handles bundling and resources is still unclear. However, it looks like Microsoft has now finalized the implementation and closed the relevant issue.

As far as I understood, the documentation on their side is still not up to date so it might make sense to wait a bit instead of relying on all the scattered information in that message chain.

[marin-bratanov]

Thank you for reaching out.

Yes, there are indications on how this will work, and we will wait for them to release the code, so we can actually play with it, and perhaps for them to ship some docs.

This is definitely on our radar, and we will document it as soon as it gets implemented in the actual codebase (after Preview 6).

[marin-bratanov]

The JS Interop file will be included as an asset from our package for the upcoming 1.2.0 release. The themes - not yet, as that requires much more work and consideration.

For the time being, the themes will keep being served through the CDN listed in the article, and when there is a change or a new way, I will update that article.

I will now close this issue through 58ed051, 2243029 and b749b28, though.

[marin-bratanov]

A quick update - we just found some framework issues - purely client-side apps can't work with static assets and asp.net core hosted client apps need additional config 5597ce1.

[TimoSalomaki]

Thanks for the update Marin, interesting development.

[marin-bratanov]

Personally, I'm a little disappointed at how uncomfortable it is - enabling the static assets is an explicit step you must make, and it does not work at all for pure client Blazor apps. Let's hope it gets improved through dotnet/aspnetcore#10986