Azure App Service Team Blog

How the App Service team functions

Custom Cultures Coming Soon to Azure App Service

In response to customer feedback the Azure App Service team is planning to add custom cultures at the end of March 2017. The culture definitions influence aspects like the writing system, the calendar, the sort order of strings, and formatting for dates and numbers.

We recommend reviewing related code paths for your apps to properly take advantage of this new App Service feature. The new cultures are differentiated by the culture name and may share the same LCID culture identifier. Sharing a 0x1000 LCID culture identifier is common with new cultures on Windows platforms and it is important to always reference cultures based on the culture name rather than the LCID culture identifier to avoid unintended app behavior.

For a small scope ASP.NET example using the System.Globalization namespace, focus on the Name property of a CultureInfo object instance for culture specific information:

var culture = new CultureInfo(“en-US”, false);

var region = new RegionInfo(culture.Name);

Using the LCID culture identifier property of the CultureInfo object instance instead would not be recommended and can result in exceptions (e.g. System.Globalization.CultureNotFoundException):

 var culture = new CultureInfo(“en-US”, false);

var region = new RegionInfo(culture.LCID);