I've bound a button to a resource using the new expression using a classKey/ressource name pair:

<asp:Button ID="Button1" runat="server" Text="<%$ Resources:ResourceWeb,MyResource %>" />

I've created 2 resource files for this. ResourceWeb.resx and ResourceWeb.fr.resx

When I change the culture using:

Thread.CurrentThread.CurrentUICulture = new CultureInfo("fr");

The button still shows the text in the default resource and doesn't switch to fr

How can we change the culture of our page dynamically when using the classKey as an alternative to the resource manager?

-- Using VS 2005 Beta 2

When do you change the Thread's UICulture? This needs to be done before the page is executed, so somewhere in global.asax such as PreRequestHandlerExeute.

-Brock

Hello.

As an alternative to what Brock said I think that you can also override the InitilizeCulture method of the Page class and do your initialization there.

I was doing it in BeginRequest and tried it in PreRequestHandlerExecute (which doesn't work).

The right solution is to use InitializeCulture.

Thanks!

DevInstinct wrote:

I was doing it in BeginRequest and tried it in PreRequestHandlerExecute (which doesn't work).

This works for me. Why is this not working for you?

DevInstinct wrote:

The right solution is to use InitializeCulture

It depends. This gets back to a similar debate that we were having over on another thread about how to initalize themes application wide. The InitalizeCulture approach requires this to be done in every page (or in a common base class) which I find to be an unappealing approach. I prefer the PreRequestHandlerExecute approach to be better, as it's application wide and outside of the page.

-Brock

BrockAllen wrote:

This works for me. Why is this not working for you?

I searched and found out why (we're like that aren't we? Can't simply continue working until we know the WHYS and HOWS).

If you've got a UI culture specified in design view thru properties, global.asax doesn't override it, but InitializeCulture does.

I agree with you that a generic approach is better, so I'd recommand not to use the design properties for culture.

Thanks again!