Home/ Questions/Q 3398712
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T04:40:58+00:00

I have a multi-language system, and all over the place I have what I

  • 0

I have a multi-language system, and all over the place I have what I would call “wrapper properties” in every class, such as:

Public Property Name(Optional ByVal ForceLanguageCode As String = Nothing) As String
    Get
        Return Translations.GetByCode(Me.EntityID, "name", ForceLanguageCode)
    End Get
    Set(ByVal value As String)
        Translations.SetByCode(Me.EntityID, "name", value, ForceLanguageCode)
    End Set
End Property

I would then copy and paste that code for every translatable field.

I am hoping to be able to replace that with one line of code somehow, with a class. The only thing that changes each time is the name of the field, such as “name”, “title”, or “subject”, etc. This seems a bit of a waste and I want my system to be as easy to use as possible for developers.

I did some research into attributes but I don’t think that is my answer as:

1) I don’t know how to automatically instantiate the objects, especially as this is extending a LINQ entity where the New() signature is already generated by the DBML. My current technique uses static functions.

2) The “EntityID” is realtime information, not compile-time.

Could anybody suggest how I could clean up this mess?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Instead of strings you can use lamdas:
    Retrieving Property name from lambda expression
    That way you at least get compiletime checking.

    You could use stackwalking to infer the calling method and thus the associated property. So you don’t need to manually refer to the property at all. But I don’t like that approach.

    You can do aspect-orientated programming with an IL rewriter like PostSharp. Then you could replace the manual code with an attribute. PostSharp then adds your boilerplate code to properites with that attribute.

    But I’m not sure if your overall design for localization is good. I’ve never seen it done this way. And I don’t understand what the setter is for.

    • 0