In this chapter, we have covered some important aspects of implementing globalization in ASP.NET 3.5. We saw that although it is easy and simple, there are a few important points and best practices to bear in mind when globalizing our ASP.NET web applications:
Do not rely on the web browser's settings. Provide a link on the application (may be in the header) so that the users can select their choice of language.
.resxfiles to separate out presentation-related data in the GUI. Resource fallback is the approach used by ASP.NET when it is unable to find the resource file for a particular culture. It will first go to the neutral resource file, and then to the default or fallback resource file.
Strike a balance between global and local resource files based on the application's needs.
We can extend the Resource-Provider-Model in ASP.NET to store localized content in database tables instead of the
.resxfiles. This gives us the flexibility to modify and update localized content easily...