A Blazor component for displaying and managing data grids with CRUD operations, supporting multiple back-end technologies.
GridBlazor is a Blazor component library for building interactive data grids with CRUD operations in .NET applications. It solves the problem of displaying and managing tabular data by providing a flexible grid that works with various back-end data sources, including REST APIs, gRPC, OData, and local data.
Developers building Blazor WebAssembly or Blazor Server applications, or ASP.NET Core MVC projects, who need feature-rich data grids with server-side processing capabilities.
Developers choose GridBlazor for its back-end agnostic design, allowing integration with C#, Java, or OData back-ends, and its comprehensive feature set including sorting, filtering, paging, and multi-CSS framework support out of the box.
Grid component with CRUD for Blazor (client-side and server-side) and ASP.NET Core MVC
Supports C# via GridCore, OData services, and Java via GridJavaCore, allowing integration with diverse back-end systems as outlined in the README's multiple back-end options.
Designed specifically for Blazor WebAssembly and Blazor Server, providing seamless .NET component usage without JavaScript interop overhead, as noted in its compatibility sections.
Compatible with Bootstrap 3/4/5, Materialize, and Bulma, enabling easy adaptation to existing design systems per the CSS framework support notes in the README.
Includes checkbox selection, keyboard navigation, and file upload columns, enhancing user experience with built-in capabilities like SetCheckboxColumn and SetKeyboard methods.
Requires managing multiple packages (e.g., GridCore vs GridMvcCore) and following specific migration guides for version upgrades, as detailed in the lengthy migration sections, increasing initial effort.
Documentation is split across different files for each back-end and environment (e.g., Blazor WASM with OData vs gRPC), making it harder to find unified guidance quickly.
Tied to specific back-end technologies (C#, Java, OData); if a project uses an unsupported data layer, integration becomes challenging without custom work.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.