Syncfusion ships a free MIT Blazor toolkit and fixes for ASP.NET Core
Serguey Asael Shinder2 min readMicrosoft's ASP.NET team announced on 29 October a collaboration with Syncfusion, the commercial component vendor, that has two parts: a free component library and engineering work on the Blazor platform itself.
The Syncfusion Toolkit for Blazor is published under the MIT licence as the NuGet package Syncfusion.Blazor.Toolkit. It contains charts, buttons, calendars, date and time pickers, text and numeric inputs, dialogs, tooltips and loading indicators. It is free for commercial use and needs neither a licence key nor eligibility for Syncfusion's Community License. Microsoft stresses that it is separate from the broader commercial Syncfusion Blazor suite. The ASP.NET team says it worked with Syncfusion on performance, accessibility, security and trimmability.
The second part is contributions upstream. According to the post by programme manager Daniel Roth, Syncfusion engineers have had changes merged across ASP.NET Core and the .NET scaffolding tools, including fixes for preserving prerendered state on interactive Not Found pages, form validation with inherited models and clearer QuickGrid diagnostics, plus scaffolding fixes for generated edit pages and Blazor Identity pages. They have also repaired flaky regression tests and run more than 60 end-to-end validation scenarios for new .NET 11 Blazor features. Two further contributions are under review: a toolkit setup scaffolder and an installation skill for the .NET skills repository used by AI coding assistants.
The pattern follows Syncfusion's earlier open-source toolkit and engineering commitment for .NET MAUI.
What it means
The fixes help every Blazor developer regardless of component choice, which is the more durable part of the announcement. The toolkit is a vendor's entry tier: the open package is deliberately a subset, and the full suite remains commercial. The first reader comment under the post was a developer saying they are removing Syncfusion components from their codebase, a reminder that quality claims are best tested in a real application.