Migration to GridBlazor 3.0.0 and GridMvc 5.0.0 Some classes have been moved from the GridMvc package to the GridCore one. You should change any reference to this property to reflect this change. The Grid property of the GridCore object has an ISGrid type, instead of SGrid it was before. You must replace all GridServer instances by GridCore ones You have to remove the package GridMvcCore and install the package GridCore, and upgrade the GridBlazor package Migration to GridBlazor 3.0.0 and GridCore 5.0.0 This is an example of a table of items using this component: Using GridBlazor component for ASP.NET Core MVC.Documentation for Blazor WASM with local data.Documentation for Blazor WASM with OData back-end.Documentation for Blazor WASM with GridCore back-end (gRPC).Documentation for Blazor WASM with GridCore back-end (REST API).You can find the specific documentation for each environment clicking the following links: There are native C# Grid components for Blazor client-side and server-side, and for ASP.NET Core MVC. Blazor WASM with data local in the client:.Blazor WASM with GridCore back-end (gRPC):.Blazor WASM with GridCore back-end (REST API):.NET Core 3.1 and 5.0 and 6.0, and Blazor WebAssembly 3.2.0 and 5.0 and 6.0 Demo All samples are based on library, but it can be any other OData provider. But GridMvcCore is only required for ASP.NET MVC projects now. GridMvcCore, that it is a fork from, was working for earlier versions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |