- 2 minutes to read
Most DevExpress ASP.NET controls include an advanced client-side API in addition to the comprehensive server-side object model. As a result, web applications based on DevExpress web controls can function more efficiently - via a combination of server-side and client-side processing.
A web control’s default client functionality (typically implemented via the internal client API) automatically performs specific actions in response to user-interactions with web control elements. For example, the ASPxMenu control displays menu items. If a user moves the mouse pointer over an item, it highlights the item and shows its submenu.
Custom client functionality allows you to manipulate web control behavior via client-side code as required (e.g., an ASPxNavBar group can be expanded or collapsed in code when needed).
DevExpress web controls synchronize property values between client and server sides regardless of where a user modifies them (on the client or the server).
We recommend that you only use the documented public client-side API to implement custom client functionality.
Client API Discoverability
A server object’s client-side equivalent uses the ‘ASPxClient‘ prefix in its name, as shown in the examples below:
You can find documentation on a specific client object by typing its name in the Document Explorer’s Index section. (As noted above, a client object’s name always begins with the ‘ASPxClient’ prefix.) The public client-side API is also documented in the Reference section of our documentation (e.g., DevExpress.Web.ASPxMenu.Scripts, DevExpress.Web.ASPxEditors.Scripts, DevExpress.Web.ASPxGridView.Scripts).