Articles

Blazor Server has a standard UX that display the reconnection status of the application, in this article I will show you one way to customize this UX.

Blazor has a few built in content areas, mainly for errors or the such, but with most things they should be customized. And this article will go over the little box at the bottom of the screen that shows when the server throws an exception.

For the past week I took the time to fork the csharpfritz/blazor-workshop GitHub project and run through the sessions but creating them in the Experimental Mobile Blazor Bindings project. The project is quite simple so it was a good project to build a Mobile client in.

We got some exiting stuff done in the Demo over the past month, we were able to get some GUI per player, stating their captured Immortals, the LeaderBoard GUI was also implemented, and a day/night cycle lighting. We also had quite a few Platform updates and the Zone had a load of Unit Testing done to get the coverage up.

In this article I will be going over State Management using an Inject Attribute in Blazor. I use this in my Blazor applications when I only want to access some sort of state from anywhere not in the context of a CascadingParameter. This is usually for components or code that is triggered by observers and could only be triggered in the context of a valid Zone.