UI for ASP.NET Core
Feature-rich grid component supporting a wrapper for ASP.NET Core.
The ASP.NET Core Responsive and Adaptive HTML5 Grid component is ready to roll right out of the box. You can enjoy over 100 features from filtering and sorting data, to advanced features like pagination and hierarchical data grouping.
Page, sort, filter, or group your data using the slick and intuitive interface of the Telerik Core Grid control. You can enable these built-in features of the Grid Control using just a few property settings.
You can enable automatic data editing for your Telerik Core Grid using the Kendo UI DataSource component, specifying appropriate update, create and destroy method definitions. Additionally, you can use the extensive API to handle the CRUD operations in a custom manner.
In-cell, inline and popup editing are supported, as well as editing via custom editors. You can enable batch editing and enable users to edit multiple items with auto-track changes and save them all by hitting a Single Save button.
In ASP.NET Corescenarios you can select between Ajax, Server or Web API editing.
Export the content of the grid control into PDF and Excel. Easily customize the look and feel of the exported file to match the user requirements.
The Frozen Columns feature of the Core Grid is useful when going through large amounts of data. It enables you to lock certain columns by simply picking Locked in the column properties. Furthermore, the Grid also automatically provides a menu to allow the user to execute unlock or lock operations.
Grant your users the ability to resize and reorder the columns you have provided them on the client, without any request to the server. In addition, the provided context menu enables them to easily hide or display, sort or filter columns.
Quickly create an N-level hierarchical Grid by specifying detail templates. Setting up a hierarchy can be done using both Server and Ajax approaches, enabling you to implement your Core hierarchical Grid component in any application. Client and server detail templates are also supported.
The ASP.NET Core Grid component has Google-style autocomplete filtering. The functionality filters records intuitively when browsing through large amount of data.
Utilize Kendo UI’s DataSource component binding your .NET CoreGrid control to static arrays, dynamic objects, local or remote data, or even SignalR hubs. Data virtualization is also supported, significantly reducing the loading time and resources needed to visualize the active view of data in the grid when having a large number of records in the source.
Binding to Web API endpoints via Server or Ajax binding is especially useful in ASP.NET Core scenarios. Custom binding is also supported.
Have full control over the way your ASP.NET Grid for Core looks to the end user. Using the template feature of the Grid you can easily customize the layout of your columns, rows, toolbar and details in hierarchy.
Why do you need to build a mobile version of your app when the same application can work equally well on mobile and desktop devices?
Provide your users with a way to interact with the Telerik Grid component in addition to using the mouse. Simply specify which keys should be used for each action and get full control over the keyboard navigation experience.
The Telerik Core Grid control is perfect for scenarios where accessibility is important for your application. The Grid complies with Section 508 and WCAG guidelines, ensuring that individuals with disabilities can still view and interact with it.
Using the ASP.NET Grid for Core, you can be certain that your app will look and behave as expected across all browsers.
Read the full list of supported browsers.
See ASP.NET Core in action and check out how much it can do out-of-the-box.
Check out the offers. Purchase an individual suite, or treat yourself to one of our bundles.
Try ASP.NET Core i with dedicated technical support.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.