Hi,
I'm currently having a problem with a Web Service application that uses
the standard .net satellite resource mechanism for loading loaclised
resources. I have a *.resources.dll in a language sub folder in the web
applications main dll directory.
I have created an entry in the web.config file for this application
that specifies the culture that should be used.
This all works fine, if the setting in the web.config is set to 'nl'
for example, the Dutch resources are displayed, if set to en-US, the US
resources are displayed.
THE PROBLEM however is that after a varying period of time (usually
about an hour) on the end users system, the resources switch back to
the default resources in the main applciation dll (in my case English
US). The only way to get the language back to what it should be is to
reboot.
I'm not sure what is causing this strange behaviour, but I have a
suspicion that it is something to do with where I'm setting the
Thread(UI)Cultu re. Currently I'm doing this in the Global.ascx.cs file
in the [Application_Acq uireRequestStat e] event. Here I read the
language from the web.config, create a culture based on it, and then
set the current thread culture and ui culture to it.
Is this the correct place to be setting the thread culture? Are there
any other reasons why I might be getting this strange behaviour (only
noticed on W2k3, and not on all systems)?
Thanks
I'm currently having a problem with a Web Service application that uses
the standard .net satellite resource mechanism for loading loaclised
resources. I have a *.resources.dll in a language sub folder in the web
applications main dll directory.
I have created an entry in the web.config file for this application
that specifies the culture that should be used.
This all works fine, if the setting in the web.config is set to 'nl'
for example, the Dutch resources are displayed, if set to en-US, the US
resources are displayed.
THE PROBLEM however is that after a varying period of time (usually
about an hour) on the end users system, the resources switch back to
the default resources in the main applciation dll (in my case English
US). The only way to get the language back to what it should be is to
reboot.
I'm not sure what is causing this strange behaviour, but I have a
suspicion that it is something to do with where I'm setting the
Thread(UI)Cultu re. Currently I'm doing this in the Global.ascx.cs file
in the [Application_Acq uireRequestStat e] event. Here I read the
language from the web.config, create a culture based on it, and then
set the current thread culture and ui culture to it.
Is this the correct place to be setting the thread culture? Are there
any other reasons why I might be getting this strange behaviour (only
noticed on W2k3, and not on all systems)?
Thanks