Custom Cultures
We know that .NET 1.1 and 2.0 support globalisation via the use of cultures, the latter being better than the former. .NET 2.0 applications support the notion of custom cultures, whereby an application developer may define a new culture. This chapter explains how we might create, register/unregister and deploy custom cultures. In the global marketplace, we need custom cultures to deal with such things as the Spanish speaking population in the USA (es-US).
This chapter presents an end-to-end example of how we might go about building our own custom culture. Small steps are used to take us through creating a new culture, installing it and uninstalling it – the example is small enough such that the code used in this chapter is now overwhelming.
One gotcha is presented in this chapter. It is a gotcha that we are all very familiar with: DLL hell. Custom cultures are all public – when you install a culture, you have no idea whether somebody else has created a culture with the same name. The author refers to this as Custom Culture Hell. Luckily, he goes on to explain a few workarounds that can alleviate this problem. One to be aware of.
Comments