Posted 21 Dec 2007
Link to this post
First off, I will tell you that making the switch from classic to prometheus will not be as easy as updating the dll and the tag prefixes. I would describe prometheus as "mostly" backwards-compatible but there will be a few areas where the server-side code will need to be revised and likely several client-side updates (if you've been using alot of client-side code).
Now, all that being said, I strongly believe it is worth the effort to do the upgrade. Furthermore, if you're using classic radEditor anywhere, then it becomes a no-brainer.
So to answer your questions directly, yes I have implemented the prometheus controls in production (virtually ever since the very first release) and have incrementally updated my projects in tune with the incremental growth of the prometheus suite. In doing so, I have been able to chop anywhere from 10% to 40% off the size of any given page, depending on the type of radControl being used and the number of them. Again, by far the biggest performance increase is in the radEditor, but the radGrid also has significant improvements.
On top of that, if you are using alot of the ASP.NET AJAX framework already or the ASP.NET AJAX Control Toolkit, or any other controls built on top of the framewor, then it becomes easier to integrate prometheus with those other controls.
Now, with respect to the viewstate errors you mentioned - those errors may not have anything to do with the radControls at all. There's lots of ways to get a garbled viewstate, each of which has a different solution. For example, if you have a button on a big page and click the button before the page has completely loaded, chances are the viewstate will be invalid. In that scenario, the advantages of having less markup rendered via prometheus controls helps to mitigate that error.
Hope that helps,