I prefer ASP.NET MVC, particularly with Razor, to WebForms. However, if I'm going to attempt to leverage the features of Telerik grids for things like exporting, etc, it appears the MVC grid lags far behind the AJAX grid in terms of functionality.
Case in point: the custom code and reliance on an open source third party project for exporting to ONLY Excel for this MVC grid sample: http://www.telerik.com/support/kb/aspnet-mvc/grid/export-to-excel.aspx vs. the many, built-in export options of the AJAX grid: http://demos.telerik.com/aspnet-ajax/grid/examples/generalfeatures/exporting/defaultcs.aspx
There is also the huge disparity of control availability b/n MVC and AJAX.
In this instance, I don't know why exporting features would have such a disparity, or why the Excel support in the AJAX can't be used in the MVC grid but it looks like if we really want to take advantage of Telerik web client controls, we're better served by using the AJAX platform rather than the MVC platform, which lags far behind.
Am I missing something, or am I correct in concluding the features of the MVC toolset lag way behind the AJAX toolset? This seems strange to me, since I've found it far easier to extend MVC with extension components and helpers than extending WebForms.
Thanks for any comments.
Case in point: the custom code and reliance on an open source third party project for exporting to ONLY Excel for this MVC grid sample: http://www.telerik.com/support/kb/aspnet-mvc/grid/export-to-excel.aspx vs. the many, built-in export options of the AJAX grid: http://demos.telerik.com/aspnet-ajax/grid/examples/generalfeatures/exporting/defaultcs.aspx
There is also the huge disparity of control availability b/n MVC and AJAX.
In this instance, I don't know why exporting features would have such a disparity, or why the Excel support in the AJAX can't be used in the MVC grid but it looks like if we really want to take advantage of Telerik web client controls, we're better served by using the AJAX platform rather than the MVC platform, which lags far behind.
Am I missing something, or am I correct in concluding the features of the MVC toolset lag way behind the AJAX toolset? This seems strange to me, since I've found it far easier to extend MVC with extension components and helpers than extending WebForms.
Thanks for any comments.