Book Review - .NET Internationalization

Windows Forms Specifics

Windows Forms Specifics
This chapter, as its name suggests is focused wholly on .NET Windows Forms. The example here, as the author confirms, is simplistic, which is a good thing. The example goes through the steps required to localise a form using the property assignment model. On the premise that the property assignment model may seem like it will have a performance impact, I was pleased to see the author include links to Brian Pepin’s Localisation Filter.

Once again, the support for internationalisation in Visual Studio 2005 shines through. However, good use of box-outs help those developers still using Visual Studio 2003. In fact, this chapter is littered with useful tips and gotchas that will make your internationisation task that bit easier.
This chapter also demonstrates that the Win32 API is alive and well. The need to invoke Win32 methods is evident when the author describes trapping the WM_SETTINGSCHANGE event. It’s worth noting that even in .NET 3.0, some Win32 API calls still have to be made; wrappers don’t exist as yet.

A good explanation of where localisation support originates is proved by means of a simple example. We are presented with the Print Preview Dialog box in both English and German. The operating system provides all of the localisation support, except for the Print Preview Dialog – which is provided by the .NET Framework and the .NET language packs.

In addition to an introduction to the WinRes tools, its pros and cons are covered. Further, the author makes some useful recommendations as far the use of the WinRes tool goes.

Surprisingly, if you’re new to internationalisation, this chapter includes a reasonably large description of ClickOnce, including a little bit about MSBuild. I suppose when you think about application deployment, tool support for internationalisation is very important – hence it’s good see it covered here.

You might also like...

Comments

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Java is to JavaScript what Car is to Carpet.” - Chris Heilmann