Activities of "easyest"

In my test project, that was based on Abp 0.6.3 I used custom attributes for that (please check attached file).

Few notes on those:

1. This was done before localization was moved to Core project, so localization source name was set using configuration, now You should be able to get it directly.
2. There are Display and DisplayName attributes - Display attribute cannot be extended, so You will need to use DisplayName attribute.
3. For localized validation attributes to work You will need to register them in You Global.asax:

DataAnnotationsModelValidatorProvider.RegisterAdapter(typeof(LocalizedRequiredAttribute), typeof(RequiredAttributeAdapter));
            DataAnnotationsModelValidatorProvider.RegisterAdapter(typeof(LocalizedStringLengthAttribute), typeof(StringLengthAttributeAdapter));

4. LocalizedDisplayName attribute can be used on enums also, original DisplayName attribute can not.

Hope that helps :) Attributes.zip

And if I am using constants? Put code into constant and use javascript translation? Translate in .Select from IQueryable in application service? Create some kind of provider, as in feature provider?

Bump

Yes. I see the index is recreated in the last migration. Topic closed.

Could You please give us an update on Your success? I need exactly the same thing - to create wcf service, but I would not like to loose abp functionality.