G
Guest
I am sure there are long chapters on this subject, but maybe someone can
quickly point me in the right direction:
When developing a pocket-pc app, is there a recommended (or simple) approach
to localizing applications? My pocket-pc application implements many
date-related operations, and the date-format differences between US and
European countries are causing problems. Currently, I have “hard-coded†the
culture info as follows:
private CultureInfo defaultCulture = new CultureInfo("en-US");
Then i repeatedly use this culture object in my code, when executing DML
with SQL CE or directly w/ SQL Server.
In ASP.NET in the WEB.CONFIG file, i can specify globalization in one
centralized attribute, and that’s it. I wonder if the same can be done when
developing apps w/ the Compact Framework rather than repeatedly specifying or
referencing the culture object in hard-code?
Thanks,
quickly point me in the right direction:
When developing a pocket-pc app, is there a recommended (or simple) approach
to localizing applications? My pocket-pc application implements many
date-related operations, and the date-format differences between US and
European countries are causing problems. Currently, I have “hard-coded†the
culture info as follows:
private CultureInfo defaultCulture = new CultureInfo("en-US");
Then i repeatedly use this culture object in my code, when executing DML
with SQL CE or directly w/ SQL Server.
In ASP.NET in the WEB.CONFIG file, i can specify globalization in one
centralized attribute, and that’s it. I wonder if the same can be done when
developing apps w/ the Compact Framework rather than repeatedly specifying or
referencing the culture object in hard-code?
Thanks,