Localization (i18N) in ASP.Net Multi-tenant SaaS application
问题 Problem scenario: Implement ASP.Net localization in a SaaS based application. Additional complexity: The tenant should be able to edit the localized content. Thus, if the hosted application has 10 tenants with each supporting 5 languages, we could end up with 50 units of translation content. Please suggest on what would be an ideal approach given the above scenario. Listed below, are approaches used in the past (for my other applications) and why they are not relevant now: Option 1: ASP.Net