Analysis of asp.net2.0 localization technology caused by Meta:resourcekey

In fact, I just look, also do not understand. Alas, the knowledge is too short, there is no way, then check the data learned:asp.net2.0 localization technology . Hey!

Referencing msnd: implicit localization

(1) Ensure that you have local resource files (. resx files) that meet the following criteria: They are located in the App_LocalResources folder. The base name matches the page name. For example, if you are using a page named Default.aspx, the resource file is named Default.aspx.resx (for the default resource), Default.aspx.es.resx, Default.aspx.es-mx.resx, and so on. The resources in the file use the naming convention resourcekeyProperty ." " . For example, the key name Button1."Text" .

(2) in the control tag, add an implicit localized property.

<asp:button id= "Button1" runat= "Server" text= "DefaultText" meta:resourcekey= "Button1"/>

All resource files are compiled, and ASP.net uses the. NET Framework Explorer at run time to retrieve culture-appropriate resources for each resource in the default resource file. For each resource, asp.net finds the corresponding resourcekeyproperty ." " combination (in the previous example) in the page resourcekey="Button1" , and then replaces the resource with the retrieved value.

Note: The CLR-generated intermediate language file is the file that will generate your code *.cs or *.vb. The. NET framework does not recognize *.cs or *.vb files and only recognizes *.resx files. resource files are used in the development of multilingual systems . </