Non-Cultural .NET Resource Hierarchy

Question

I have some string resources, for example. user greeting line. By default, this should be "Hello", but for client X, it should be "Greetings."

I would like to use . The implementation of NET resources , and the lines will sit in constants or in files or wherever I like, plus the hierarchy model meets my needs: client X resources redefine the user's welcome line.

The only problem is that the .NET resources seem to be i18n oriented, and they choose from a hierarchy based on the current culture.

At the moment, I will keep flat resources for each client and display the hierarchy on my own, but is there a better solution?

Answer 1

Nothing really prevents you from having multiple ResourceManager, but as you say, it was designed for l18n. Personally, I had a lot of problems with resx stuff, especially when it came to GAC builds and deployments. Another problem I am facing is the rigidity of this system, if you need a new line, you need to recompile dll and muck around with xml, your clients do not have the flexibility to fix it, there is something that is there to maintain time.

, , , resx , "en-US" "en" , , , , "en- " . , "en-US" X "en-AU" Y, , , .

-.

, , sqlite mssql, .