Hey,

Please explain me something: why the text properties of the web components aren't marked with the Localizable attribute? In the windows control collection they are, so it's not like you didn't know about standard ways to work with .NET localization tools.

A suggestion was made in support center (DS23521) in that regard... almost one year ago. Not only I think it's been a LONG time it should have been done, I believe no one should have had to tell you in the first place! This should have been easy to guess that on the web I may want a multi-cultural application, and that I would expect to be able to do it in the same way as with .NET basic controls.

Even the poorly designed MS gridview control has column with localizable headertext property!

Okay, right, you had some other stuff to do. Besides, I think you are doing a nice job on windows components. They're great, easy to use, makes an overall good impression on the users. I give you that. With your web components, however, I'm pretty disapointed. Quality is far inferior to their windows siblings, and that's something I'm not used to with DevExpress, who again made a wonderful job on the WinForm side.

I'm not talking about new AspXperience components; so far it looks like they will have a brighter future. They still misses a few things (like localization, again!), but I won't be too hard there because it's still in it's early versions. On the other hand, AspxGrid and data controls suite look more like something you have to keep making work the way it does now because of, maybe, early development bad decisions and/or retrocompatibility reasons (I'll admit it's pretty hard to do otherwise for web components) and less like reliable, scalable and easy to use controls.

By the way, do you have any live example of it's usage in a public web application? (Not the demos!)

Anyway... I'm getting away from my main point: localization. To me it's a major issue because it's elementary, basic .NET design stuff that should have been fixed a long time ago since it's relatively easy to do (it's just adding a Localizable attribute, isn't it??). It would be okay if you missed a few (even today), but hey, even the label control's text property isn't localizable. It's really THAT bad!

I truly hope I won't have to wait another year before seeing this fixed. No way I'm doing my website's localization in two different ways!

Sorry if my english is bad.