Where Are We?

In this chapter, we covered the internationalization issues that are specific to Windows Forms applications. You learned how to use Visual Studio to make forms localizable and to localize them, and you saw that this rests on the resource technology we discussed in the previous chapter. We looked at the different serialization models used by Visual Studio 2003 and Visual Studio 2005, and we compared their relative merits and implementations. We looked at how the user can specify the user interface culture, and how an application can cope with its culture changing without having to restart the application. We saw that the .NET Framework's dialog components and classes depend on the operating system or .NET Framework Language Pack for their resources, and that this can be either a curse or a blessing, depending on your application. We looked at the Windows Resource Localization Editor and saw that it is a great tool that can be made to work with a little thought. Finally, we looked at the way ClickOnce deploys localized applications and saw that localized applications need some additional attention to get the most from this powerful technology.