Localization in asp.net 2.0

Summary:

As more and more multinational companies require cross-language Web applications, localization becomes particularly important, and in ASP.net 1.1 we use the ResourceManager class to do this, and 2.0 provides more convenient methods and tools to implement.

Introduction:

Now many multinational business needs need to implement multi-language, for customers they always want to see the site is displayed in their familiar language, they will not pay attention to what the site is using the technology, and the current development tools or development technology does not do a good job in localization, we still need to spend a lot of Time and effort to do localization work.

The advent of asp.net2.0 greatly simplifies this process, with vs.net2005 new features, we can easily get the automatic stripping of the language elements of the site, it is easy to implement multiple versions of the site, and many for the localization of the API can also be convenient to help us complete this process

Localization in. NET 1.1:

In 1.1 We use ResourceManager to implement this process, and perhaps for WinForm this process is relatively simple, but vs.net2003 does not give us the webform of localization work to bring about what automation, We also need to spend a lot of effort on duplicating the code.

Localization in. NET 2.0:

Localization in 2.0 is still based on 1.1, but it provides a lot of automation work:

1. Automatically generate page resource files

2, convenient programming to achieve the access of resource files

3, automatically load the appropriate language for the page

4. Automatic matching of controls and resource files

5, strongly-typed resource files

6. resource File Editor

7. Use Expression of resource file

8. Resource Provider Model