Let me again shed some light on the questions asked:
We have few things in development that will allow some, if not any of the requested features (at least implementing them in a correct way, some of them are dependable on runtime features that are not there at the moment):
+ Double Derivation:
this is a special code generation technique that derives a 'base class' and a inheritor (your actual class), and marks all base properties as virtual. That way guys you will be able to override the generated code form OA in the following manner:
...so you can augment the generation the way you want, where required.
+ Automation for: System.ComponentModel.DataAnnotations attributes, INotifyPropertyChanged/INotifyPropertyChanging. What automation means is that we will provide wizards and other infrastructure so that you can setup those for yourselv through the designer.
+ Ria /ADS support - we know this is very important and we are hectically working on that. I hope we will have descent support in the DevConnections event timeframe (~ one month)
+ VS 2010 support (~ one month)
Please provide me with more information on 'No concept of Interceptors' that you mentioned earlier. If you refer to the ADS interceptors, we will have them in the Ria/ADS time-frame already mentioned, If you refer to something else, please explain.
Regarding the comparison document EF/OpenAccess ORM, I guess we should provide that when we see the final bits of EF 4.0?
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.