C# 4 and .NET 4

Windows forms localization Using Visual studio ❘ 589
public BookOfTheDayForm(string culture)
{
if (!String.IsNullOrEmpty(culture))
{
CultureInfo ci = new CultureInfo(culture);
// set culture for formatting
Thread.CurrentThread.CurrentCulture = ci;
// set culture for resources
Thread.CurrentThread.CurrentUICulture = ci;
}
WelcomeMessage();
}
InitializeComponent();
SetDateAndNumber();
code snippet BookOfTheDay/BookOfTheDayForm.cs
The BookOfTheDayForm is instantiated in the Main() method, which can be found in the file Program.cs.
In this method, you pass the culture string to the BookOfTheDayForm constructor:
[STAThread]
static void Main(string[] args)
{
string culture = String.Empty;
if (args.Length == 1)
{
culture = args[0];
}
}
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new BookOfTheDayForm(culture));
code snippet BookOfTheDay/Program.cs
Now you can start the application by using command-line options. With the running application, you can
see that the formatting options and the resources that were generated from the Windows Forms Designer
show up. Figures 22-10 and 22-11 show two localizations in which the application is started with the
command-line options de-DE and fr-FR, respectively.
There is still a problem with the welcome message box: the strings are hard-coded inside the program.
Because these strings are not properties of elements inside the form, the Forms Designer does not extract
XML resources as it does from the properties for Windows controls when changing the Localizable
property of the form. You have to change this code yourself.
figure 22-10 figure 22-11
www.it-ebooks.info