Using a Database for Localization

We have seen how to localize the text of the controls and the application content in the UI. But sometimes, the content is stored in a database, and this content also needs to be localized (for example, when using a Content Management System). Because this content is stored in a database, we cannot use resource files for this. Sometimes we may not be able to use resource files at all because we might want to avoid an application recompilation or restart when updating localized content (remember that updating a resource file under the /bin folder will cause an application recompilation or an application restart.).

Also, using a database gives us the flexibility to edit content easily as there are no resource files involved. We can create a simple edit form, so that content authors can edit and update the content without having any programming knowledge.

Custom Resource-Provider-Model in ASP.NET

When we use a database instead of .resx files to store the...