Problem Scenario:
Implementing ASP.Net localization in a SaaS-based application.
Additional complexity: the tenant must be able to edit localized content. Thus, if the hosted application has 10 tenants, each of which supports 5 languages, we can get 50 units of translation content.
Please suggest what would be the ideal approach, given the above scenario.
The following are the approaches used in the past (for my other applications) and why they are not relevant now:
Option 1: ASP.Net Resource Files
Problem: Only one language file is created for a localized resource (.aspx page). Therefore, it is not possible to have one Home.aspx.resx file for each tenant transfer. Although resx keys can be modified to contain TenantId (lblFirstName_44) and stored in the same resx file, then it will be difficult to maintain, and we can get large files.
Option 2: Saving multilingual content in dedicated database tables (labels, messages, menu items)
:
( , ). , - . (, , )
( .Nets)
3:
, FairlyLocal
:
, , .resx - , () .
. , , , 2