Wrappers vs Widgets

From a client-side point of view, the vanilla HTML/JavaScript Kendo UI widgets and their ASP.NET MVC wrappers (UI helpers) represent the same thing and provide the same capabilities.

However, before choosing one product over another, you need to consider existing implementation specifications.

List of Pros and Cons

Telerik UI for ASP.NET MVC Wrappers

The Telerik UI for ASP.NET MVC helpers (Kendo UI MVC wrappers) provide the following benefits:

  • They enable you to create widgets with no HTML and JavaScript coding. JavaScript knowledge is still required if you want to apply client-side methods and events.
  • They provide for server-side data binding and in some cases, server-side rendering.
  • You can use the ToDataSourceResult extension method to bind Kendo UI widgets to server-side collections, and perform data operations such as paging, sorting, filtering, and grouping.
  • They provide integration with some ASP.NET MVC features such as security trimming, localization with resource files, or editor templates.
  • They support unobtrusive validation based on Data Annotation attributes.
  • Implementing CRUD operations is simple. The support for CRUD data operations requires less coding as compared to when the client-side Kendo UI is used. In the latter case, you have to repeat the model and data field configuration in the JavaScript code.
  • The Visual Studio IntelliSense is available for the server-side configuration syntax.
  • They enable Visual Studio Extensions for automatic creation of new Kendo UI ASP.NET MVC applications, or adding Kendo UI to existing projects, or automatic updating of the Kendo UI version.
  • You are able to use scaffolding to generate widget declarations and related controller action methods.

Kendo UI Widgets

The vanilla HTML/JavaScript Kendo UI widgets (Kendo UI Professional) provide the following benefits:

  • They allow for a complete server-platform independence. The widgets can be used with any web server and server framework—including ASP.NET MVC. For example, you can build Single Page Applications with any RESTful backend.
  • They provide full control over the placement of the initialization scripts—server wrappers render the widgets' initialization scripts right after the widget's HTML output. Even if you use deferred initialization, the scripts are still kept in the View. When using plain (non-wrapper) Kendo UI widgets, you write the initialization scripts yourself and can move them to external script files.
  • They support the integration with the MVVM, AngularJS, and Single Page Application development patterns. Server-side wrappers are not intended to be used with these.
  • Visual Studio IntelliSense is supported for the client-side API.


You can use Telerik UI for ASP.NET MVC helpers and vanilla Kendo UI widgets at the same time on the same page, if a specific scenario requires that.

See Also

In this article
Not finding the help you need? Improve this article