Why should you use IHttpClientFactory The main reason to use IHttpClientFactoryinstead of HttpClient directly is to manage the life cycle of HttpClient instances. HttpClient was designed to be instantiated once and reused throughout the application life cycle. If you continually instantiate new HttpClients you may unnecessarily be squandering resources. Another use case is for simplicities…
Adding HealthChecks to your application can drastically reduce troubleshooting time Why would you want to monitor your applications health? Health checks can test an applications dependencies, such as databases and external service endpoints, to confirm availability and normal functioning. From Microsoft Out of the box Health Checks UI Here is how to monitor SQL Server…
Table of Contents Why is IHttpContextAccessor -or- HttpContext sometimes null on Blazor Server? The IHttpContextAccessor on Blazor Server is only available on the first Http request when loading a Blazor Server application. After that, all connections to the server is handled via SignalR. Your HttpContext will most likely be null after this. This may be…
The answer is pretty simple once you understand the page life cycle of a Blazor applcation Lets start with a sample Razor component that renders the UI: Component.razor Lets look at the ‘code behind’ (ooof I’m old) AKA a partial class that represents the logic of the component (view) Component.razor.cs Looks pretty normal right? The…
You need to have a MudRadioGroup to contain your MudRadio buttons. On the MudRadioGroup you have the @bind-SelectedOption event callback exposed. You can set a switch statement on that to dynamically render your other components. Parent Component: TestComponent.razor Sample Project https://try.mudblazor.com/snippet/wOmRucPSpMDbtnAw
