Telerik UI for Blazor – 100+ truly native Blazor UI components for any app scenario, including a high-performing Grid. Increase productivity and cut cost in half! Give it a try for free.
Recently I was asked to be part of a panel discussion on Blazor by Ed Charbeneau, Senior Developer Advocate at Progress. I'll talk about Blazor at literally any opportunity so I, of course, said yes!
In this post, I'm going to show you how to create bespoke input components for your Blazor applications. We'll look at how to integrate with Blazor's validation system, but also, how to work outside it.
In this post, I'm going to point out a couple of limitations with using Blazor's input components as is. I'll then show how you can build your own custom input components to solves these problems.
In this post, I'm going to show you how you can build your own convention based router component to replace the default router that ships with Blazor.
In this post, It take a deep dive in the nuts and bolts of routing in Blazor. Starting in the JavaScript world where navigation is intercepted and following the code into the C# world to the point of rendering the correct page or the not found template.
In this post, I begin to look at how navigation works in Blazor. I start by showing the differences between navigation in traditional web apps vs SPAs. Before taking a high level look at Blazor's router component and how a navigation request is handled.
My book, Blazor in Action - an example-driven guide to building client-side web apps using C# and .NET - is available to buy.
All the latest posts delivered straight to your inbox.
