3 Answers, 1 is accepted
0
Hello Kirk,
You should use the Behaviors property. The property name was changed from singular to plural, as the property is a [flags] enum which allows for multiple values - as suggested by the ASP.NET conventions.
Kind regards,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
You should use the Behaviors property. The property name was changed from singular to plural, as the property is a [flags] enum which allows for multiple values - as suggested by the ASP.NET conventions.
Kind regards,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Martin
Top achievements
Rank 1
Rank 1
answered on 19 Feb 2009, 02:21 PM
Hi, this thread helped me too.
I was wondering what should I use instead of Behavior.
Next time something is marked obsolete in code, please insert a message in the ObsoleteAttribute, indicating what to use, or why this is obsolete. This way, this can be corrected by the users, without having to search about it. The message will be written with the warning about the method / property being obsolete.
Example:
I was wondering what should I use instead of Behavior.
Next time something is marked obsolete in code, please insert a message in the ObsoleteAttribute, indicating what to use, or why this is obsolete. This way, this can be corrected by the users, without having to search about it. The message will be written with the warning about the method / property being obsolete.
Example:
| [Obsolete ("Use property PropertyName instead.")] |
| public Type SomeProperty |
| { |
| get { return someValue; } |
| set { someValue = value; } |
| } |
0
Hello Martin,
Yes, you are right. We usually do this for all obsolete properties, but we've missed this one - we apologize for that.
By the way, this property will be removed from Q1 2009 next month - it has been marked as obsolete for almost year and a half and it is time to remove it.
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Yes, you are right. We usually do this for all obsolete properties, but we've missed this one - we apologize for that.
By the way, this property will be removed from Q1 2009 next month - it has been marked as obsolete for almost year and a half and it is time to remove it.
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.