Visual Studio .NET

.NET localization is based on creating satellite assemblies; there is one satellite assembly (dll) for each language. Satellite assemblies are compiled from resource (ResX) files. Visual Studio .NET form designer automatically creates ResX files, if form's localizable property is set to TRUE.

How does Multilizer localize .NET applications

Multilizer can localize

  • .NET resource files (ResX localization), and
  • .NET assemblies (binary localization)
ResX localization
ResX_Localization.gif
On localizing ResX files Multilizer can read (c) individual ResX files, (b) ResX files of a project, or (a) ResX files of the solution's projects. Multilizer writes out either (A) localized ResX files or (B) compiled satellite assemblies.
Binary localization
Assembly_Localization.gif
On localizing a .NET assembly Multilizer reads the compiled resources from the assembly and writes out (compiled) satellite assemblies.

[Read more about localization process...]

Determining startup language of the assembly

In Winforms applications the form designer created code takes care of loading the resources from the satellite assemblies; the software tries to use the satellite assembly matching user's locale settings. If this fails, software starts in default language, i.e., the language of the main assembly.

Developers can write code to start the software in a specific language. Dcalc sample that is included in Multilizer setup shows how to pass the startup language as a command-line parameter.