Blazor StateHasChanged() Jan. 4, 2019
On this episode of Blazor StateHasChanged() we explored validation using the FluentValidation package. Validation is still a concept in Blazor that has no subscribed best practice, however existing libraries like FluentValidation are possible solutions. On the show we test FluentValidation with both WebAssembly and Razor Components with success. We also looked at how to create a toast notification component by following along with Chris Sainty’s article.
Blazor Toast Notifications using only C#, HTML and CSS
Read more on Chris’s Blog about Building Blazor Toast Notifications
Blazor/Razor Compiler updated
Ryan Nowak tweeted that a new Razor compiler was completed and merged. This change replaces the legacy Blazor compiler with the new, shiny, built-in support being developed over at aspnet/AspNetCore-Tooling.
We reached a major milestone last night in Blazor/Razor Components. We're now building and running components with the official Razor compiler. https://t.co/mkUO0HJQbY— Ryan Nowak (@aVerySpicyBoi) January 2, 2019
Next up: In-the-box VS Support!@DamianEdwards @stevensanderson
Blazor Quick CMS
Robert Sundström created a CMS that uses Blazor and Markdown files for a “quick” content management experience. Check out his app and source code on GitHub.