Resource files are the key for internationalization. Consult the help file
for more info. It is very similar to the C++ string table, but a bit more
flexible.
As for the second question. The norm for resource files, with
globalization/localization, is to set up a file for each language. Look at
MSDN, as there are plenty of examples on this, including setting up a
framework that automatically grabs default language settings when there are
none in the particular language the user has his machine set to use.
You will find that much of the globalization work is done for you in the
..NET Framework. Rather than reinvent the wheel, study the help file, as well
as the MSDN articles. The Culture objects will save you from writing a ton
of code. Well worth the time.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"kensmtih1976" <ks****@daktronics.com> wrote in message
news:8a**************************@posting.google.c om...
I have done multi lingual support in C++ and now I am trying to figure
out how to do in C#.
In C++, there were the string tables where you could enter text in
multiple languages, and now I want to have similar functionality in
C#. What is the equilvalent of string tables in C# resources?
Also, you could make a copy (different language for each copy) of a
dialog/menu in C++ resource editor and I want to do the same thing
with Windows Forms in C#, how can this be done?