Last post Jan 27, 2010 12:57 AM by Song-Tian - MSFT
Jan 25, 2010 10:03 AM|megetron|LINK
I have an articles website, and there is a requierment to make it one website that will support differend databases.
The same code will be publish to different domains, and according to the domain name, the website will choose it's own web.config file, themes, database and so on...
The databases has the same table design, so the DAL code should not be changed....
There are some problems I can think of, like what happens when I have a UserControl with ASP:IMAGE object that points to the images directory, and how to change it to point on the images directory inside the app_theme folder, and I guess there are much more
to think of when designing such.
can you please give me some instruction and some of the tasks I will have to handle in such project?
any suggestion will be greatly appriciate.
Thank you all,
Jan 27, 2010 12:57 AM|Song-Tian - MSFT|LINK
Implicit localization (on the Visual Studio - Tools menu - Generate Local Resources) is about as easy as it can be. Write your pages in your default language, pick the menu option, and your resource files are created and can be sent to someone to translate.
The resx file is just xml, so if the translation company wants you can transform it into (and out of) spreadsheets easily.
Using a databases instead of resx as your backing store is not difficult. Rick Strahl has a good explanation and example code for a database-driven localization provider
here - there's a nice built in localization editor too with interface to Google translations and Babelfish.
For more details, please check:http://www.beansoftware.com/asp.net-tutorials/globalisation-multilingual-cultureinfo.aspx .