Skip to end of banner
Go to start of banner

Custom Language in Core

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Version History

Version 1 Next »


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')


Install Custom Language to Local Machine

Trips and Pitfalls



Filter by label

There are no items with the selected labels at this time.