Localized resource files

In addition to modifying the standard resource files, you can create localized resource files by adding the appropriate language and culture code to the file name. Infor Operations and Regulations uses the culture name codes defined for the CultureInfo class in the .NET Framework. For example, a localized Asset Management resource file for Australia would be called Hansen.AssetManagement.en-AU.Resources .

If localized resource files are present, IIS uses the culture code from the Infor Operations and Regulations site’s ASP.NET configuration to determine which resources to use. To check or set the culture code, open the site in IIS Manager and select the .NET Globalization feature. The culture code is displayed in the Culture and UI culture fields.

Infor Operations and Regulations will use the resource files that are localized for the site’s culture if they’re present in the bin directory. Otherwise the standard resource files will be used. For example, Infor Operations and Regulations would first attempt to use Hansen.AssetManagement.en-AU.Resources for an Australian site, and would then use Hansen.AssetManagement.Resources if the localized file isn’t found.

Localized resource files can be placed directly in the bin directory, or they can be placed in a subfolder that is named with the appropriate culture code. For example, Australian resource files can be placed in either bin or bin\en-AU.