Location>code7788 >text

Implement multilingual under .Net in an alternative way

Popularity：947 ℃/2025-02-23 23:19:07

Preface

There are already many mature solutions for multilingual solutions under .Net, such as: #Avalonia's internationalization path: In-depth application and exploration of Resx resource files,or#Avalonia uses XML files to achieve internationalization, basically all are implemented around the official Satellite Assembly solution. In fact, we can implement multilingual in a very primitive way.

step

1. Resources resource file generation

Create the following text file (assuming it is)

Greeting=Hello

Copy the tool directory of the framework (you can see it by searching for everything) to the current directory and execute the following command

PS D:\workSpace\Code\test\resx>.\.\
 Read in 1 resources from ".\"
 Writing resource file... Done.

You can get our first step。

illustrate:
The tool also supports resx files. For specific use and reference the official document of /en-us/dotnet/framework/tools/resgen-exe-resource-file-generator. In fact, this is also called behind msbuild when editing the IDE we use. tool.

2. Dll file generation

With the resources resource file, we can link the resources resource file into a dynamic link library through the linker (also in the framework's tool directory).

PS D:\workSpace\Code\test\resx>.\ -target:lib -embed:.\ -out:
 Microsoft(R) Assembly Linker version 14.7.2053.0
 Copyright (C) Microsoft Corporation. All rights reserved.

illustrate:

  1. -target:libRepresentative products are library
  2. -embed:.\Represents the generation resource file that has just been embedded
  3. -out:Represents the name of the product
  4. Open it with ilspy to see the embedded resource file.
  5. Note that we do not specify it here-culture:zh-HansParameters, and the official documentation says that this parameter must be passed (/en-us/dotnet/core/extensions/create-satellite-assemblies）Because we do not use the .net language resource mechanism at all, and we do not have to follow its hub-and-spoke model (referring to the relationship model of the center of the wheel and the spokes of the wheel, that is, the positional relationship between the main dll and the satellite resource dll Model)
  6. Here we need to have a certain understanding of the structure of dlls under .Net, you can refer to the pictures in the previous link.
  7. Can also be used-template:To specify the metadata template for generating the dll, otherwise the generated dll is in the metadata table in ilspyTypeDefWill display<Module>Such unnamed records.
  8. We are using a linker here, but we can actually use a compiler (this is the case under .net core), refer to the previous link.

3. Use

Create a console application, the code is as follows:

using System;
 using;
 using;
 using;
 using;

 namespace ConsoleApp1
 {
     internal class Program
     {
         static void Main(string[] args)
         {
            // Manually load the assembly generated by the linker
            Assembly ass = (@"D:\workSpace\Code\test\resx\");
            // The first parameter "rex" is the file name we embedded, and the second parameter is the application assembly
            ResourceManager rm = new ResourceManager("rex", ass);
             var s = ("Greeting");
             (s);
         }
     }
 }

The output is:

Hello

 D:\workSpace\Code\test\resx\ConsoleApp1\bin\Debug\ (process 5184) has been exited with the code 0 (0x0).
 Press any key to close this window. . .

You can get the language resources we defined.

illustrate:

  1. Since we are loading it by hand, = new CultureInfo("en-us");This has no effect at all. Similarly, the linker's cultrue parameter does not affect it. You can test it yourself.

How to:

After reading this and the reference materials in the article, it should be of great help to everyone to understand the multilingual of .Net. Next is my plan (maybe nonsense)
If you want to manage the entire sln language resources in one file (for example, special requirements), you can customize the Task through msbuild (you can compare the process of automatically generating code in the Grpc proto file edited. In fact, Google is the same. (or combined with the following T4 template?) directly generate ResourceManager dictionary for all languages. The encapsulation method returns the resources of the corresponding language. If you have special needs, you can try it yourself. If it doesn't work, just think I'm talking nonsense.

<Previous Next>