Error Parsing Raditem

[Richard]

hello folks,

Environment:

• VS2012
• Windows 8

Just upgraded to Latest version of Winforms controls, 2012.3 1017, upgrade went fine, but now when I open certain forms in my project designer gives a number of different errors: see attached.

This only happens on certain forms, but these forms aren't doing anything ground breaking and have mostly the same types of controls, buttons, listbox / grid, text boxes, etc.This error causes run time issues as well.

Have any of you run across this at all?

Richard

[Jack]

Hi Richard,

This issue is caused by the fact that we changed the internal element structure in some of our controls in Q3 2012. Please, find the full answer to your question in your support ticket regarding the same issue.
 
All the best,
Jack
the Telerik team

[Bob]

I am experiencing the same problem on various forms.
Can I get the answer/solution to resolve this problem.

Regards,
Bob

[Stefan]

Hello Bob,

As my colleague Jack states this is cause by changes in the element tree of some controls. This changes causes issues in properties serialized through the Element Hierarchy Editor at design time. Removing these serialized properties should solve the issue. If this does not work for you, please send us your project and we will look into it for you.

Kind regards,
Stefan
the Telerik team

[Bob]

Thanks for sharing the information.  However I'm not sure what you mean by removing serialized properties.
Can you provide further explanation on how to do such a thing?

Thanks

[Stefan]

Hello Bob,

If you have used the Edit UI Editor of any RadControl to introduce some setting, this will serialize your setting in your form designer file. With the new changes, those serialized settings is what is causing the error mentioned. If you remove them from the designer, the error should be resolved.
 
All the best,
Stefan
the Telerik team

[Michael]

I also have the same problem with setting properties on the RadListView.  Not being able to use the element hierarchy editor to change property settings is an important bug, and is unacceptable.  When is this going to be fixed?

I am using 2012.3 1211.40

[Stefan]

Hello Michael,

You are able to change setting vie the Element Hierarchy Editor. The issue comes from the fact that if you had such settings introduced prior Q3 2012 they will cause this error and you have to remove them from your designer, rebuild the form and apply them once again to the desired elements or in code.

This is needed because we have changed the control element structure in Q3 2012 and the serialized settings will points to wrong elements which will cause such errors.

I hope this helps.

Greetings,
Stefan
the Telerik team

[Laura]

I was using 2012.2.912.40 and upgraded to version 2012.3 1211.40. Now I am also experiencing the same problems due to setting changes in the controls.

Do you have a list of the controls that these changes applied to and which portions of the serialized properties need to be removed and readded? I assume I would have to do the element removal and readd in code since the form has errors after the version update.

Thanks,
Steve H

[Svett]

Hello Stephen,

There is no particular list. When you introduce changes to the controls element tree via the UI, those changes are serialized in design time as lines accessing the children of the tree and setting some properties to them. You basically need to remove all lines in the designer file, where elements from the Children collection are modified.

Additionally, if you want to follow up with anything new, you can use our release notes here.

I hope this helps.

Greetings,
Svett
the Telerik team