Cesar Guinovart
Top achievements
Rank 1
Rank 1
Cesar Guinovart
asked on 13 Sep 2007, 04:38 PM
I noticed after I installed the current 3.5.3 BETA that some TreeView members were marked as deprecated (They might have been there before but i didn't notice).
What do you recommend to use instead in both cases? Is there a replacement or something else that should be used?
The reason i am asking is i am trying to clean up an existing VS Solution of warnings to turn "Treat warnings as errors" and i will need to change the code to whatever is that should be used once the BETA is released.
Thanks in advance..
What do you recommend to use instead in both cases? Is there a replacement or something else that should be used?
The reason i am asking is i am trying to clean up an existing VS Solution of warnings to turn "Treat warnings as errors" and i will need to change the code to whatever is that should be used once the BETA is released.
Thanks in advance..
1 Answer, 1 is accepted
0
Hi Cesar Guinovart,
As the obsolete message for both properties states, the setters will be removed from the public API of RadTreeNode. That is necessary because by using these setters one can damage the treeview structure. This is why we decided to handle setting these properties internally.
The getters will remain and are safe to be used. Unfortunately, the obsolete attribute cannot be applied to the setter only. That is, even if you only use the getter of these properties (and not the deprecated setters) you will still get warnings.
We will most probably wait another Q release and then remove all obsolete members.
I guess you will have to wait till then.
Best wishes,
Jordan
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
As the obsolete message for both properties states, the setters will be removed from the public API of RadTreeNode. That is necessary because by using these setters one can damage the treeview structure. This is why we decided to handle setting these properties internally.
The getters will remain and are safe to be used. Unfortunately, the obsolete attribute cannot be applied to the setter only. That is, even if you only use the getter of these properties (and not the deprecated setters) you will still get warnings.
We will most probably wait another Q release and then remove all obsolete members.
I guess you will have to wait till then.
Best wishes,
Jordan
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center