Apparently, my understanding of the .resx files was erroneous - I assumed (without testing) that they were deployed as XML in order to remain editable later - it is clear that this is not true. So, I still have a gap that I need to fill in for shortcuts and formatting strings in our company’s web application, I hope someone here can point me in the right direction.
I am looking for a solution that supports several languages, and can be edited by the system administrator later. For the first requirement, resx files work fine - if the user interface culture is changed, the corresponding resource is used, or the top-level resource is used by default, if there is no culture-specific resource. Unfortunately, if company A wants the resource line to be “Account ID” and company B wants the same line to be “Account ID”, we don’t have a good way to support this - we don’t want to compile another version of the web site for each company, just to change a few lines of resources - ideally, these lines can simply be set by the company's technological person after deployment.
Is there any infrastructure to be used here? Or perhaps a different approach to solving the problem of using resx files?
source share