Blazor

Infragistics Joins Blazor With Free Open-Source Components

Infragistics has made more than 50 of its Blazor controls free and open source under the MIT license, and its engineers are contributing directly to the framework. New .NET 11 analyzers from the collaboration are merged into ASP.NET Core, so every Blazor developer gets the tooling benefits, whether or not they use its components.

.NET Blog Daniel Roth
Published
Reading time
3 min read
agent run #14
agent run #14
Go to original devblogs.microsoft.com

Report this story

Is something wrong with the summary, or do you own this content? Your message comes straight to my inbox.

Type of message

Key points

  • More than 50 Ignite UI for Blazor controls are free under the MIT license, including for commercial apps
  • Core controls install with: dotnet add package IgniteUI.Blazor.Lite
  • Grid Lite for tabular data installs separately: dotnet add package IgniteUI.Blazor.GridLite
  • Blazor Web Apps need an interactive render mode for these components
  • New .NET 11 analyzers flag unnecessary StateHasChanged() calls and stale authentication-state usage
  • An Ignite UI setup scaffolder is under review, and an AI agent skill is in the .NET skills repository

Microsoft and Infragistics are now collaborating on Blazor. Infragistics has opened up more than 50 of its Ignite UI for Blazor controls under the MIT license, so they can be used in personal and commercial projects. This free set is a subset of the commercial suite rather than a trial. It includes inputs, navigation and layout controls, along with Grid Lite for tabular data.

The contributions also reach the framework. Infragistics engineers added .NET 11 analyzers that flag needless StateHasChanged() calls and authentication-state usage that can leave stale user data on screen. They are merged into ASP.NET Core, so every Blazor project benefits. A setup scaffolder is under review, and an Ignite UI skill for AI coding agents is in the .NET skills repository.

Real-world use

  • Adding date pickers, combo boxes and tree views to an internal Blazor Web App without buying a commercial suite
  • Showing a filterable user or team table in an admin dashboard with Grid Lite
  • Catching unnecessary StateHasChanged() calls and stale auth-state usage at build time in a team moving to .NET 11

Why it matters

Blazor developers can evaluate free, MIT-licensed components for production apps. The .NET 11 analyzers also help catch common Blazor mistakes at build time, even if you never use Infragistics controls.

This summary was generated by the agent from the original post on .NET Blog. The full text and all rights belong to its author and publisher. Go to original

Related stories

Feedback

Found a bug or have an idea? Your message lands straight in my inbox.

Type of message