Data Binding Overview
The Telerik UI for ASP.NET Core Menu provides flexible data binding capabilities that allow you to populate its items from various data sources. You can choose the appropriate binding method based on your application architecture and data requirements.
The default casing for JSON strings in ASP.NET Core is camelCase. The Telerik UI components that are data-bound depend on PascalCase formatted response from the server. If the JSON serialization isn't configured properly, the UI components will display wrong data. To find out how to configure the application to return the data in Pascal-case, refer to the JSON Serialization article.
Data Binding Approaches
The Menu supports the following data binding methods:
Items Binding
Define the Menu items declaratively within the component configuration when using:
- Declarative menu structure with known items.
- Static navigation content that does not require external data sources.
For detailed implementation instructions, refer to the Items Binding documentation.
Model Binding
Bind the Menu to a local dataset by passing an arbitrary model directly within the boundaries of the component. This approach is optimal for small to medium-sized datasets that can be loaded in memory.
For detailed implementation instructions, refer to the Model Binding documentation.
Remote Data Binding
Connect the Menu to a remote endpoint using AJAX requests. This enables:
- Dynamic menu generation using server-side data.
- Real-time menu updates based on user permissions or roles.
- Improved performance with large menu structures through on-demand loading.
For more information and examples, refer to the Remote Data Binding documentation.
Custom Attributes Binding
Implement custom attribute binding for enhanced Menu functionality by applying model binding to populate menu items dynamically from the server while binding HTML attributes to model fields:
- Bind the Menu items to model properties and specify custom HTML attributes.
- Apply client-side logic based on item attributes and selection.
- Create Menu hierarchies with additional metadata.
- Enable attribute-driven Menu behavior and interactions.
For more information, refer to the Custom Attributes Binding documentation.
Data Binding in Razor Pages
You can seamlessly integrate the Menu component into Razor Pages applications. All the data binding approaches described above can be configured within Razor Pages scenarios.
The component supports both HtmlHelper and TagHelper syntax, and allows you to send the anti-forgery token when connecting to remote endpoints to ensure secure data operations.
For detailed implementation instructions, refer to the Razor Pages Binding article.
Key Considerations
When selecting a data binding approach for the Menu, evaluate the following factors:
- Performance—Items binding offers fastest initial rendering for static Menus, model binding provides fast rendering for local data, while remote binding delivers better performance with large datasets through server-side operations.
- Data volume—Items binding works best for small static Menus, model binding suits small to medium-sized datasets, while large menu structures are better handled with remote binding.
- Data structure—Items binding is ideal for known static hierarchies, model binding works well with server-side collections, while remote binding supports dynamic data from any endpoint.
- Customization needs—Custom attributes binding enables enhanced functionality when Menu items require additional metadata and client-side logic based on attributes.
- Security—Remote and model binding provide better control over data access and validation compared to Items binding.
- Real-time requirements—Remote binding is essential for scenarios requiring live data updates and dynamic content refresh.