I am really confused and aggravated by this error that apparently is a bug in the current release (Quarter 2, 2009), as evidenced on page 156 of the "RadControls for ASP.NET AJAX" developer's manual, "Handling ViewState Conflicts." It states, in part, that "one last wrinkle that you may run into is that as your control tree becomes more complex...[you're screwed]."
I have 5 RadGrids on a webform and I simply want them to work. However, after the page loads, the grids are filled with data, and when any row or menu item is selected, the application crashes because of this "little wrinkle."
So I copied your work-around code to kill viewstate on control first load, but (damnit!) you only give an example FOR ONE CONTROL!!! What about the more likely event that there will be multiple controls on a page? How is that addressed?
And then, at the bottom of page 157 in the work-around code, where the hell does IDynamicControl come from? It's not in the APIs of System.Web.UI nor Telerik.Web.UI and fails to compile.
Finally, there is no mention of this "little wrinkle" in the RadGrid section of the manual - I stumbled upon the above entriely by chance.
Sheesh!!!
I have 5 RadGrids on a webform and I simply want them to work. However, after the page loads, the grids are filled with data, and when any row or menu item is selected, the application crashes because of this "little wrinkle."
So I copied your work-around code to kill viewstate on control first load, but (damnit!) you only give an example FOR ONE CONTROL!!! What about the more likely event that there will be multiple controls on a page? How is that addressed?
And then, at the bottom of page 157 in the work-around code, where the hell does IDynamicControl come from? It's not in the APIs of System.Web.UI nor Telerik.Web.UI and fails to compile.
Finally, there is no mention of this "little wrinkle" in the RadGrid section of the manual - I stumbled upon the above entriely by chance.
Sheesh!!!