Developing Internationalized .NET Apps

To support the Global users most of the application developed needs to support Internationalization. Let us examine the key guidelines

Set the CurrentUICulture and CurrentCulture properties in the application explicitly. Do not rely on the default value.



  1. ASP.NET applications can use the same classes as other managed applications for retrieving, displaying and manipulating information based on the culture.



  1. Specify the following values – requestEncoding , responseEncoding, fileEncoding, culture and uiCulture attributes in the following 3 places in ASP.NET application as mentioned below



    1. Globalization section of web.config file. This file is external to the ASP.NET application



    1. Page Directive. Note that when the application is in a page, the file has already been read. It does not make any sense in specifying the fileEncoding and requestEncoding. Only uiCulture, Culture and responseEncoding can be specified in a page directive


    1. Programmatically in application code. This setting can vary per request. As with a page directive, by the time the application's code is reached it is too late to specify fileEncoding and requestEncoding. Only uiCulture, Culture, and responseEncoding can be specified in application code.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.