Member Avatar for Shreya J

Hello All ,

I am working in a project in which I have been asked to use Telerik Gridview control.
I was curious to know that why should we use Telerik Controls when we can do the same thing using ASP controls.

Like in gridview the collapse and expand feature etc.

Please guide me.

Is there any extra feature or advantage of using these that's not present in ASP controls ?

Thank You in Advance.

Regards ,
Shreya.

  • 2 Contributors
  • 2 Replies
  • 127 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Shreya J

Dani AI

Generated

asked whether Telerik controls are worth using instead of plain ASP.NET controls, and correctly hinted that not every project needs them. The practical difference is not that Telerik does something impossible — it packages a long list of polished, production-ready UI behaviors so teams spend far less time building, testing, and maintaining them.

  • Rich client-side behavior and built-in AJAX: sorting, paging, filtering and inline editing can happen without full postbacks, reducing custom JavaScript and round-trips.
  • Master/detail and hierarchical grids: detail templates, expandable rows and nested tables are provided out of the box.
  • Advanced grid features: grouping, multi-column sorting, column menus, frozen columns, column reordering, and virtualization for very large datasets.
  • Export and printing: built-in export to Excel/PDF/CSV and print-friendly output.
  • Theming, localization and accessibility: consistent skins, RTL/localization support and keyboard/ARIA considerations.
  • Documentation and support: demos, samples and vendor support speed onboarding and troubleshooting.

Trade-offs to consider: licensing cost and vendor dependency; larger client-side footprint if many widgets are used; and occasional upgrade work when major framework versions change. For a simple CRUD form or a tiny table, the ASP.NET GridView plus a few jQuery plugins may be lighter and cheaper. For enterprise dashboards, complex reporting, or apps where consistent advanced UX must be delivered quickly, Telerik often pays for itself in saved development and QA time.

A pragmatic path: build a one-screen prototype using both approaches, measure development time, page size and responsiveness, and factor in license/support costs and long-term maintenance. If dataset size is large, enable virtualization and prefer server paging/binding where appropriate. For teams under tight deadlines or needing polished features, Telerik is a sensible choice; otherwise stick with native controls or lightweight JS components.

Member Avatar for Cruize_Invades

I did use Telerik before.

Is there any extra feature or advantage of using these that's not present in ASP controls ?

only few.

Member Avatar for Shreya J

Ok... I would like to know the advantages in detail.

It will be great if u can detail it a bit.

Thank u...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.