Custom Language in Core

Disney language:
- .net language must be installed on machine which builds the solution - if not - it doesn't generate the satellite localization dlls.
Even though the resx files are included into the main dll, the app (web) doesn't access them.
- Create dll which just does the language registration so we can use a powershell script to execute on build (build action).
Check in the custom culture generator dll to 'lib'
Visual Studio - restart to let VS update the .NET language list (especially removing a language)

Sisulizer Tool

We have one license of the software (currently installed on Stefan-PC). It creates translations (resx files) for Visual Studio solutions. Every custom language (i.e. en-US-Disney) needs it's extra set of resource files, generated by Sisulizer.

• Add a new language variant
• Export resx files into checked out solution/project
• Manually add all resx files to the solution/project
• Set the Custom Tool and Custom Tool Namespace for each resx file to match the original neutral resx files.
• Check in the new resx files
• Check in/update the Sisulizer configuration file ('MarineLMS - Sisulizer Translation.slp')

Update Resx Files and/or Make Translations

1. Open Sisulizer project file /src/MarineLMS - Sisulizer Translation.slp
2. Project → Scan for Changes 
3. Select All to view all text which can be translated.
4. 
5. Ctrl + F5 to search for any term you need to translate
6. Make any translation/changes you need
7. Project → Build in Selected Language will generate the updated/new resx files
8. Save the Sisulizer project
9. Open MarineLMS solution in Visual Studio
   1. Include newly created custom language specific resx files (created by Sisulizer) to MarineLMS solution
      1. The easiest way to find any new resx files created by Sisulizer is to check Sourcetree for uncommitted changes/unstaged files
      2. In VS, right click resx file and select Include in Project (enable Show All Files in the Solution Explorer)
   2. 
   3. Update the newly added resx file's properties (2) to match the values of the counterpart's resx file (= default language resx file)
      1. Custom Tool
      2. Custom Tool Namespace
   4. Example: if you added AssessmentSummaryRx.en-US-Disney.resx, there is always a resx file AssessmentSummaryRx.resx.
10. 
11. Commit all resx files and the Sisulizer project file /src/MarineLMS - Sisulizer Translation.slp and /src/MarineLMS - Sisulizer Translation.sds

Install Custom Language to Local Machine

Trips and Pitfalls

Related articles