N-Tiered.NET Application Localization Instructions

Question

I would like to get some of your ideas about

• resource name / categorization
• place of resources

Let me just provide you with the scope:

• 3 or more supported languages
• 3 MVC websites [with lots of shared resources as well as some unique resources]
• 1 common MVC extension library
• 1 core business library with common functionality and business objects [also contains resources]
• 3 business libraries that have specific business logic for three websites [also with resources]
• 1 The SQL 2008 database, distributed across all websites, sometimes sends localized emails.

I would like it to be easily supported (just as easily exported / imported for translation), and not duplicated (since we have common resources) and understandable for everyone who comes into contact with the code

Resources Location:

• Should I create one assembly containing all the translations? And create a link to this assembly in my projects (even if it is possible to add it to the SQL server)?
• or should I use a source control to sync all resource files?
• some other ideas?

resource name / categorization:

Thus, we have localized emails, button text (command texts), tags, error messages, informational messages, etc. etc.

, ? , ?

Answer 1

; . , , <% $Resources: zzzz% > aspx/ascx.

, , (, "" : (Token, Locale, Application, NativeText)). , , .

, ( , ), / ( , - , , ).

- , , , ; . , .

Answer 2

, - , . , - 1, , - 2 3, 2 3 - , , - , , , , , - , .

, , , , . , , :

• 1 , , -.
• 3
• 1 , -,
• 3 - , -.

, , , , , . , , .

. , , , .

SQL Server, , , , - ? , . , SQL Server , , , , .

, , ( ) . , , , , -, , , . , , , , , .

Answer 3

, , , , .

, , .pot ( nant script).