Localization stopped working. Why?

  • Thread starter Thread starter cyberco
  • Start date Start date
C

cyberco

WM5 PPC, .Net CF 2

I have resources for 2 languages in my application. I have a general
..resx file for the complete project and a .resx file for each form.
Changing the regional settings on my phone worked fine. The application
changed its language. But suddenly this stopped working. I assume
because I'm missing some resources or so. How can I check what's going
wrong?
 
It turned out I had 1 form that was not 'localization' enabled. Still,
is there a better way to find out why localization isn't working? Trial
and error can be very time-consuming.
 
I have a similar issue with an application (WM5/.NET CF 2.0).
In my case the ressource files are working correctly if I deploy the
application to the device from within Visual Studio 2005.
If I deploy the application to the device using a CAB file only one language
is used.

In my case I don't think the ressource files (.dll) are build correctly into
the cab file. It seems that the ressource file from one language is used to
build the dll's for all languages.
The inf file for the cab project looks OK to me.

Is this your experience too?

Regards,
Mikael
 
Coincidently I ran into the same error after solving the non-localized
form problem. The problem was that the localization files were not
included in the CAB. You can solve this by adding 'Localized
resources' to the CAB (right-click on the cab in the 'solution
explorer', choose 'add/project output...' and choose 'Localized
resources' from the list.

Cheers!
CyBerco
 
I have already added the localized ressources as output in the cab project.
The "Build Action" property of the the ressource files in the application
project are all set to "Embedded Ressource".

The dll files in the \bin\release\<language>\ and the
\obj\Release\<language>\ directories are localized correctly.

The cab contains a number of ressource files (dll's), but the content of the
files are the same.
- I would have expected each file to be the localized (using the dll from
the \obj\Release\<language>\ directory), but the are not.

Regards,
Mikael
 
Back
Top