In this post we were able to demonstrate how to maintain different components as separate libraries which could be imported into the main shell in order to allow modular distributed development.
It is currently impossible to implement the gRPC HTTP/2 spec in the browser because there are no browser APIs with enough fine-grained control over requests. Well the good news is that gRPC-Web is here for the rescue!
I recently ran into an issue where running a Blazor WebAssembly application under unsupported browsers would simply get stuck on the loading page. Whereas older browsers are supported under the “Server Side” model, it would be a much better experience to present the user with a more meaningful indicator that the browser is not supported.
Based on the current implementation, Blazor Router makes routing much easier to implement and developer hardly need to maintain routing as the application evolves. Bugs due to misconfiguration of routing might become a thing of the past.