First of all I should point out that the Fluent Mapping API is still in a beta phase, even though we plan on releasing a stable version in the next service pack. The point I want to make however is that decorating you classes with attributes is a bit troublesome. Also this approach, known as Forward mapping is something we will not be putting effort into.
At the time we are dedicating our time and resources to the new domain model as well as the fluent mapping API. This means that the new features and improvement will only come in the fluent mapping.
This being said, the forward mapping is stable and the fluent mapping is in beta, and currently it does not support inheritance scenarios, even though this will soon be included in the product.
Please have in mind that my previous statements are given assuming that you were talking about the old attributes(FieldAlias, Persistent etc..). However we do have a new attributes mapping approach with completely new attributes that are being generated if you select "Attributes Mapping" in the Visual Designer. You could use those attributes for forward mapping as well. You could see more information on the matter in the following section of our documentation.
It is up to you to decide what approach you will be using. Hope this helps.
All the best,
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