Optimizing RadControls for MVC

[DGDev]

Hi there guys,
I've recently started a project using ASP.NET MVC and am so far loving every aspect of it. Telerik's controls are surprisingly compatible for the most part, however, I'd like to get advice from the Telerik team as to the best way to optimize RadControls for the MVC framework.

It's obvious that you should set "EnableViewState" = "False" on each control.
I've also noticed that I had to set "EnablePartialRendering" = "False" on RadScriptManager.

My main goal is to reduce the page size and the amount of data coming back from Telerik.Web.UI.WebResource.axd
I'm still getting data set into a hidden ViewState element though. Is there an official "MVC Optimization" blog post or thread?

Much thanks!

-Danny

[Dallas Sehlhorst]

Hi Danny,

You don't need to set EnableViewState to False, or EnablePartialRendering as the events that create the ViewState are not called/used in ASP.NET MVC.

As for the ViewState still being set from the RadScriptManager, put this in your View and it will disappear (at least it does for me):

<script runat="server">
    public override void VerifyRenderingInServerForm(Control control)
    {
    }
</script>

I haven't seen a consolidated MVC performance thread, but if you look in the Telerik blogs you will find posts on how to optimize the controls in MVC.  I also find that if you use JQuery instead of the standard Microsoft AJAX your page sizes (and subsequent calls) will be less, and the pages seem more performant.

If you have any other questions, I'd be glad to help.

Thanks,

-Dallas

[DGDev]

Thanks for your help Dallas.
Unfortunately, that bit of code (method override) did not remove the ViewState element.  Also, if I don't set EnablePartialRendering to False, than Firebug reports the dreaded error: "Sys is not defined". Setting it to false fixes that problem.