Installation problem with multi-language

[=?Utf-8?B?SWFu?=]

Hi,

I am trying to display two different versions of a VB screen, one with
English prompts, one with Japanese, depending on a Radio Button setting at
login. The radio buttons just change the CurrentUICulture of the Current
Thread from default to Japanese, or vice versa. This works fine in the
development environment, but when packaged up into a setup and installed
through Windows Installer, the application doesnt seem to know of the
existence of the Japanese screen and just displays default (i.e. English).
Any idea why? The resource files are all distributed as 'embedded resource'
which means they should be part of the main assembly. I thought the setup and
runtime would handle this automatically, but it seems there is something else
to do. Any idea what I should be doing or might have missed out?

Incidentally, there is no problem with Fonts - all the machines used to run
the app have MS-Mincho installed to render the Japanese characters.

Thanks

Ian

[=?Utf-8?B?SWFu?=]

Seem to have solved this now. Looks like embedded foreign language resources
are not quite so embedded as claimed. There is a "ja-JP" folder in the bin
directory of the project that contains different dll's for the projects that
contain foriegn language screens. Include that folder and its files as a
subdirectory of the application directory in the setup, and the language
change works fine.

Thanks

Ian

"Ian" wrote:

Hi,

I am trying to display two different versions of a VB screen, one with
English prompts, one with Japanese, depending on a Radio Button setting at
login. The radio buttons just change the CurrentUICulture of the Current
Thread from default to Japanese, or vice versa. This works fine in the
development environment, but when packaged up into a setup and installed
through Windows Installer, the application doesnt seem to know of the
existence of the Japanese screen and just displays default (i.e. English).
Any idea why? The resource files are all distributed as 'embedded resource'
which means they should be part of the main assembly. I thought the setup and
runtime would handle this automatically, but it seems there is something else
to do. Any idea what I should be doing or might have missed out?

Incidentally, there is no problem with Fonts - all the machines used to run
the app have MS-Mincho installed to render the Japanese characters.

Thanks

Ian