NOTE .NET 2.0 in C#.NET

Drawer QR Code 2d barcode in C#.NET NOTE .NET 2.0

To install a culture that you create, a few things must be considered. According to MSDN, a custom culture can be registered on a computer only by a user who has administrative rights on that computer. Consequently, typical applications cannot create a custom culture. Instead, use the CultureAndRegionInfoBuilder class to build a tool that an administrator can use to create and register a custom culture. After the custom culture is registered on a computer, use the CultureInfo class to create an instance of the custom culture just as you would a predefined culture.

Using the CultureAndRegionInfoBuilder you can create a culture totally from scratch, base a new culture on an existing one, or use an existing one entirely. The code shown next illustrates how to use an existing culture.

CultureAndRegionInfoBuilder object In the previous lessons, simply having a reference and including System.Globalization as a using or Imports statement was all that was needed. However, this approach will not work here. If you try to instantiate an instance of the CultureAndRegionInfoBuilder class, you will get a type not defined error. You need to add a specific reference to the sysglobl.dll, which is usually located in C:\Windows\.NET Framework\[VERSION]\sysglobl.dll.

' VB Dim DemoBuilder As new CultureAndRegionInfoBuilder("en-US", _ CultureAndRegionModifiers.Neutral) // C# CultureAndRegionInfoBuilder DemoBuilder = new CultureAndRegionInfoBuilder("en-US", CultureAndRegionModifiers.Neutral);

All you need to do is instantiate a new instance of the CultureAndRegionInfoBuilder class, use an existing culture, and specify a CultureAndRegionModifiers value, which

will be discussed shortly. You can also use existing RegionInfo objects, CultureInfo objects, or both to populate a CultureAndRegionInfoBuilder object. This is illustrated in the following code:

' VB Dim USCulture As New CultureInfo("en-US") Dim USRegion As New RegionInfo("en-US") Dim DemoBuilder As New CultureAndRegionInfoBuilder("en-US", _ CultureAndRegionModifiers.Neutral) DemoBuilder.LoadDataFromCultureInfo(USCulture) DemoBuilder.LoadDataFromRegionInfo(USRegion) // C# CultureInfo USCulture = new CultureInfo("en-US"); RegionInfo USRegion = new RegionInfo("US"); CultureAndRegionInfoBuilder DemoBuilder = new CultureAndRegionInfoBuilder("en-US", CultureAndRegionModifiers.Neutral); DemoBuilder.LoadDataFromCultureInfo(USCulture); DemoBuilder.LoadDataFromRegionInfo(USRegion);

If you want to create a customized culture of your own, the process is not much different than the one just shown. The first thing you need to do is figure out what you want to call the culture and determine whether it will be based on an existing one. So let s say we wanted to create a new culture based on United States English specific to Microsoft Corporation. The following code illustrates how to do this:

' VB Dim USCulture As New CultureInfo("en-US") Dim USRegion As New RegionInfo("en-US") Dim DemoBuilder As _ New CultureAndRegionInfoBuilder("en-US-Microsoft", _ CultureAndRegionModifiers.None) DemoBuilder.LoadDataFromCultureInfo(USCulture) DemoBuilder.LoadDataFromRegionInfo(USRegion) // C# CultureInfo USCulture = new CultureInfo("en-US"); RegionInfo USRegion = new RegionInfo("US"); CultureAndRegionInfoBuilder DemoBuilder = new CultureAndRegionInfoBuilder("en-US-Microsoft", CultureAndRegionModifiers.None); DemoBuilder.LoadDataFromCultureInfo(USCulture); DemoBuilder.LoadDataFromRegionInfo(USRegion);

All that s being done here, in its simplest form, is creating a new culture (en-USMicrosoft) and basing it on the en and US definitions. Afterwards, we can set any properties that we want to, such as CurrencyName, CultureName, NumberFormat, or any other available properties.

16

To use the CultureAndRegionInfoBuilder class, the constructor takes an argument from the CultureAndRegionModifiers enumeration. This is a very straightforward enumeration with only three values. According to the MSDN documentation, they are each defined as shown in Table 16-3.

Table 16-3

Description A neutral custom culture A specific, supplemental custom culture A custom culture that replaces an existing .NET Framework culture or Windows Locale

If you wanted to use an existing culture but no region, you would specify the Neutral option. If you were going to specify supplemental information for the object, you would specify None (so that the amount of information inherited would be minimal). If you were going to do a replacement, you would specify Replacement, which would mandate that you set all the properties yourself.

In this lab, you ll create a culture of your own. If you encounter a problem completing an exercise, the completed projects are available on the companion CD in the Code folder. 1. Open Visual Studio 2005. 2. Create a new console application in Microsoft C# 2005 or in Microsoft Visual Basic 2005. Visual Basic 2005 creates a module for you, along with an empty Main procedure. Visual C# creates a Program.cs class for you with an empty Main procedure. 3. Make sure that the System and System.Globalization namespaces are referenced by the project. 4. Add a reference to sysglobl.dll, as described earlier in this chapter. 5. Within the Main procedure, add the following code:

' VB Dim USCulture As New CultureInfo("en-US") Dim USRegion As New RegionInfo("en-US") Dim DemoBuilder As New CultureAndRegionInfoBuilder("x-en-US-sample", _ CultureAndRegionModifiers.None)