Last post Feb 16, 2007 11:26 AM by JulianMadle
Feb 16, 2007 04:19 AM|JulianMadle|LINK
Whilst I realise the benefits of compiling gloabl resources into DLL files, this does not suit my needs. I require editability in my distribution so that end-users can change the text throughout the application and even add extra languages; however the core
code of the application must be compiled. I know that local resource files remain editable, which is great, but it still leaves problems with application-wide text - I really don't want to translate the same pieces of text in every local resource. I am using
multiple master pages, so many application-wide bits of text can be placed in the local resources for the master files, however this still results in repetition between the master file local resources.
Is there any way to attach an extra local resource file programmatically, ie. I have a local resource file names ApplicationWide.resx (plus language derivatives) which I attach to every master page (or detail page using a BasePage class)?
Any other ideas also welcome!
Feb 16, 2007 08:43 AM|max.janssen|LINK
We had the same issue, so we decided to store our global resources in a database. For this, you will need to write your own Custom Resource Provider, or use one from the examples that are available on the web. See e.g.
Only drawback with this method I have encountered so far is that you seem to lose strongly typed access to the resources in your code-behind. I have not found out how to solve that.
Hope this helps.
Feb 16, 2007 11:26 AM|JulianMadle|LINK