Referring to your forum post of the same title it is stated:
Q3 2011 (Version number: 2011.3.1115)
Probem: When adding items to OData enabled controls (RadMenu, RadTreeView, RadListBox, RadComboBox) through design time erroneous markup is applied to the control:
Solution: Remove the ODataSetting section and the issue will vanish. The problem is also fixed in the Q3 SP1 release, version number 2011.3.1305
Well sorry, but that is not true. I have 2011.3.1305.40 installed and still experienced the problem with RadMenu. Only when I deleted the OData markup did this error disappear.
Incidentally, I was pulling my hair out for some time over this error as I could only think there was a reference somewhere in the project to an older version dll as well as 2011.3.1305.40. This error should never have appeared in any release, so how come it got through all the QA process?
Jonathan
Q3 2011 (Version number: 2011.3.1115)
Probem: When adding items to OData enabled controls (RadMenu, RadTreeView, RadListBox, RadComboBox) through design time erroneous markup is applied to the control:
Solution: Remove the ODataSetting section and the issue will vanish. The problem is also fixed in the Q3 SP1 release, version number 2011.3.1305
Well sorry, but that is not true. I have 2011.3.1305.40 installed and still experienced the problem with RadMenu. Only when I deleted the OData markup did this error disappear.
Incidentally, I was pulling my hair out for some time over this error as I could only think there was a reference somewhere in the project to an older version dll as well as 2011.3.1305.40. This error should never have appeared in any release, so how come it got through all the QA process?
Jonathan
1 Answer, 1 is accepted
0
Hello Jonathan,
The error happens due to insufficient markup declarations and this markup is added by a weird bug in the RadMenu/RadListBox/RadTreeView/RadComboBox designer. It is normal that the control throws an error when the markup in not correctly defined. What is wrong here is that that markup was added the controls at all. This is what we have already fixed. What will do for the upcoming release is to handle the insufficient markup error more gently and only expose it trough the WebServiceFailed event.
Please accept our apologies for all the inconveniences caused.
Kind regards,
Genady Sergeev
the Telerik team
The error happens due to insufficient markup declarations and this markup is added by a weird bug in the RadMenu/RadListBox/RadTreeView/RadComboBox designer. It is normal that the control throws an error when the markup in not correctly defined. What is wrong here is that that markup was added the controls at all. This is what we have already fixed. What will do for the upcoming release is to handle the insufficient markup error more gently and only expose it trough the WebServiceFailed event.
Please accept our apologies for all the inconveniences caused.
Kind regards,
Genady Sergeev
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now