Hi,
In the version notes of RadControls for ASP.NET AJAX 2011.3 1115 it states:
What happened to backwards compatibility?
In the version notes of RadControls for ASP.NET AJAX 2011.3 1115 it states:
Breaking Changes
- Fixed: RadGrid column's UniqueName property should throw an exception if its value contains spaces
Indeed this is 100% correct, it has broken my project. Not only do I have to revise the uniquename's in the aspx pages but also the usage in the code behind. To make things worse, if a uniquename is NOT specified, the datafield is used. If my datafield in the DB happens to have spaces, Telerik will autogenerate a uniquename WITH spaces, only to report an exception afterwards...
What happened to backwards compatibility?
1 Answer, 1 is accepted
0
Hi Rik,
I understand your concern. We usually strive to provide strong backward compatibility. This particular breaking change was a hard decision for us to make too. Having spaces in the UniqueName of columns caused a great lot of problems that were hard to identify and generated excessive amount of support.
The value of the UniqueName property in a grid column is used in many places in the control logic, both on the server and client side and including in server control IDs and HTML element id attributes. Spaces are not allowed in many of these places a column's UniqueName can be used. Developers were complaining of broken functionality and unexpected behavior without, what seemed to be an explicable, reason.
We had to do something about this. The most reasonable decision was to disallow spaces in the UniqueName. I hope the community will understand the need for this action. As much as we hate to break developers' code, we also want them to have properly functioning controls at all times.
Greetings,
Veli
the Telerik team
I understand your concern. We usually strive to provide strong backward compatibility. This particular breaking change was a hard decision for us to make too. Having spaces in the UniqueName of columns caused a great lot of problems that were hard to identify and generated excessive amount of support.
The value of the UniqueName property in a grid column is used in many places in the control logic, both on the server and client side and including in server control IDs and HTML element id attributes. Spaces are not allowed in many of these places a column's UniqueName can be used. Developers were complaining of broken functionality and unexpected behavior without, what seemed to be an explicable, reason.
We had to do something about this. The most reasonable decision was to disallow spaces in the UniqueName. I hope the community will understand the need for this action. As much as we hate to break developers' code, we also want them to have properly functioning controls at all times.
Greetings,
Veli
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