One more comment on RadPageLayout which really make the control useless for any serious development work ... any control contained within it's scope can't be selected in the Designer. This is a serious flaw IMHO, and not really a "feature request".
Similar issue with the RadGrid NOT rendering in the designer ... because of this rather serious limitation, we're having to make changes to xml/html code (even just very minor ones), then run our app just to see those changes and verify they are what we want. This is incredibly tedious and a huge waste of time ... this isn't why we bought and/or renew our Telerik subscriptions, your tools are supposed to make development faster, not slower.
Many of your controls suffer from "property overload" ... too many options/properties some conflicting with each other while key necessities like rendering in the designer are ignored. This is not what we want, we're looking into alternatives and/or just going back to using Microsoft's set of controls.
I don't know who makes the feature implementation decision choices at Telerik, but that person doesn't seem to be aware the less is "more" ... we need easy to implement and intelligent features that "just work".
Not trying to be harsh because I thought that perhaps Telerik's overload philosophy was just Silverlight, but I see it's extended and really seems to have infected all your product line. I think Telerik has lost focus of what rapid development means? Most developers I know have bigger fish to fry than being sucked into the quagmire that is Telerik overload of properties.
Not all bad, you folks have some good features, but you also have way too many features that really should be encompassed and not exposed, embrace AI in your products to make intelligent decisions on layout.
My 2 cents, Rob.