Skip to main content

Creating a Custom Culture using .NET



Namespace: System.Globalization

CultureAndRegionInfoBuilder class provides the facility to create new and customize existing cultures.

To install a custom culture one must have administrative privileges. One must Add Reference of sysglobal.dll in order to create objects of CultureAndRegionInfoBuilder.

CultureAndRegionInfoBuilder vCulture = new CultureAndRegionInfoBuilder(“en-US”, CultureAndRegionModifiers.Neutral);

OR

CultureInfo vCultureInfo = new CultureInfo(“en-US”);
RegionInfo vRegionInfo = new RegionInfo(“US”);

CultureAndRegionInfoBuilder vNewCulture = new CultureAndREgionInfoBuilder( “en-MS”, CultureAndRegionModifiers.Neutral);

vNewCulture.Load(vCultureInfo);
vNewCulture.Load(vRegionInfo);


CultureAndRegionModifiers Enumeration:
Class
Description
Neutral
A neutral custom culture.
None
A specific, supplemental custom culture.
Replacement
A custom culture that replaces an existing .NET Framework culture or Windows Locale.

To create a culture from scratch one must go for CultureAndRegionModifiers.Replacment.

And one must only use the CultureAndRegionInfoBuilder only when the culture intended to be created does not already exists.

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...