Getting Started

Re: Where to set/change page's culture prior to FrameworkInitialize()?

Fredrik N — Thu, 29 Dec 2005 17:17:31 GMT

It was my fault, you are absolutely right Brock. It will work at the PreRequestHandlerExecute. I was confused when I read the other thread where he posted the “Session state is not available in this context" message and the code of the Application_PreRequestHandlerExecute. I assumed the problem was that he tried to use the Session within an event where the Session wasn’t ready to be used yet, like the Application_Start etc.

So thanks Brock for pointing this out.

Re: Where to set/change page's culture prior to FrameworkInitialize()?

BrockAllen — Thu, 29 Dec 2005 15:05:40 GMT

Fredrik N wrote:

At the PreRequestHandlerExecute the Session variables is not yet available for use.

Actually Fredrik, this is incorrect. Session *is* available in PreRequestHandlerExecute. The HttpApplication fires AcquireRequestState, PostAcquireRequestState then the PreRequestHandlerExecute event. Either PostAcquireRequestState or PreRequestHandlerExecute would be valid locations to use Session. The other is Application_AcquireRequestState in global.asax, as the events there are guaranteed to be called after any modules event handlers.

-Brock

Re: Where to set/change page's culture prior to FrameworkInitialize()?

martin. — Thu, 29 Dec 2005 14:12:36 GMT

Works great with the profile feature. Thank you very much!

Re: Where to set/change page's culture prior to FrameworkInitialize()?

Fredrik N — Thu, 29 Dec 2005 09:15:22 GMT

At the PreRequestHandlerExecute the Session variables is not yet available for use. What you can do is to store the culture into a cookie or maybe if you already use the Profile feature, you can use it to store the language a user has selected. You can also instead of the PreRequestHandlerExecute try to use the Application_AcquireRequestState.

Take a look at the following posts:

http://fredrik.nsquared2.com/viewpost.aspx?PostID=153

http://fredrik.nsquared2.com/viewpost.aspx?PostID=309

Re: Where to set/change page's culture prior to FrameworkInitialize()?

martin. — Wed, 28 Dec 2005 22:24:23 GMT

I can't get it to work when I want to set the prefered languange in global.asax. I've tried both memberships and session. Membership always i nothing, and when I try to use sessions i get the error "Session state is not available in this context"

What am i doing wrong here?

This is in my global.asax in Application_PreRequestHandlerExecute

If Session("culture") IsNot Nothing Then
Try
Dim ci As New Globalization.CultureInfo(Session("culture").ToString)
System.Threading.Thread.CurrentThread.CurrentUICulture = ci
System.Threading.Thread.CurrentThread.CurrentCulture = ci
Catch ex As Exception
System.Threading.Thread.CurrentThread.CurrentUICulture = New System.Globalization.CultureInfo("sv-se")
End Try

End If

Re: Where to set/change page's culture prior to FrameworkInitialize()?

wpclueless — Fri, 30 Sep 2005 08:31:42 GMT

I have tried this and it works for a listbox selection and a button, but when I try it using an image button it fails in the application_prerequesthandlerexecute saying that session state in not available in this context - any ideas why?

Re: Where to set/change page's culture prior to FrameworkInitialize()?

blackpuppy — Sat, 28 May 2005 03:36:18 GMT

First, your resx files need to be named like this (notice the dot before resx):

Register.aspx.en-CA.resx
Register.aspx.fr-CA.resx

I guess they are just typos.

My Global.asax is shown below.

<%@ Application Language="C#" %>
<%@ Import Namespace="System.Globalization" %>
<%@ Import Namespace="System.Threading" %>

<script RunAt="server">
    // other methods are ommitted for brevity.

    protected void Application_PreRequestHandlerExecute(object sender, EventArgs e)
    {
        try
        {
            string lang = (string)Session["Language"];
            //Page.Culture = lang; // This does not work! Must assign Thread.CurrentThread.CurrentUICulture!
            Thread.CurrentThread.CurrentUICulture =
                new CultureInfo(lang);
        }
        catch
        {
        }
    }
</script>

You do not need to write the prototype yourself. You can let Visual Studio do that for you. There are two dropdown list above the code pane. In the left dropdown list, select "Application". And then in the right dropdown list, select the event handler you want such as "PreRequestHandlerExecute". The event handler stub will be created for you. Then you can write your code inside.

Hope this is of some use to you.

Re: Where to set/change page's culture prior to FrameworkInitialize()?

bizbiz — Fri, 27 May 2005 14:46:16 GMT

Can you give me an example of your global.asax file ?

I have a page with 4 resources like this :
Register.aspx.resx
Register.aspx.en-CAresx
Register.aspx.fr-CAresx
Register.aspx.fr-FR.resx

When I put a break point in the Page_load event, the resource manager is load with the Register.aspx.resx. But my currentCulture is en-CA and the uiCulture is en. Anyone can help me ?

Do you write the keyword new ? Because it give me a warning if I don't do that.

new void PreRequestHandlerExecute(Object sender, EventArgs e)

{

   // create culture preference cookies if they don't exist yet
   // otherwise set current thread to value of those cookies
   System.Web.HttpCookie cookie = Request.Cookies["QuickStartLocalize"];

   if (cookie != null)
   {
      try
      {
         string currentUICulture = cookie.Values["UICulture"];
         string currentCulture = cookie.Values["Culture"];

         if ( currentUICulture != null && currentUICulture.Length > 0)
        {
            System.Threading.Thread.CurrentThread.CurrentUICulture = new System.Globalization.CultureInfo(currentUICulture);
         }

         if ( currentCulture != null && currentCulture.Length > 0)
         {
            System.Threading.Thread.CurrentThread.CurrentCulture =new System.Globalization.CultureInfo(currentCulture);
         }
      }
      catch (System.Exception)
      {
      }
   }
}

Re: Where to set/change page's culture prior to FrameworkInitialize()?

blackpuppy — Sat, 14 May 2005 10:55:49 GMT

Thanks, Fredrik!

I like the implicit expression because it will save more typing.

In addition, the web.sitemap.resx and its localized resources need to be put in App_GlobalResources folder. (I'm using Beta 2.)

Zhu Ming

Re: Where to set/change page's culture prior to FrameworkInitialize()?

Fredrik N — Fri, 13 May 2005 10:06:45 GMT

Take a look at this post on my blog.

Re: Where to set/change page's culture prior to FrameworkInitialize()?

blackpuppy — Fri, 13 May 2005 10:01:06 GMT

I have another question. Is there a way to localize web.sitemap?

Thanks!
Zhu Ming

Re: Where to set/change page's culture prior to FrameworkInitialize()?

blackpuppy — Thu, 12 May 2005 08:30:09 GMT

It works! The only drawback is that the input such as content in a TextBox will be gone after the redisplay of the same page. The user has to enter it again.

Thanks, Brock!
Zhu Ming

Re: Where to set/change page's culture prior to FrameworkInitialize()?

BrockAllen — Thu, 12 May 2005 04:28:39 GMT

Yep and for that last problem I always take the hack approach of Response.Redirect(Request.Path) to make the browser come back in so they see the changes immediaetly.

-Brock

Re: Where to set/change page's culture prior to FrameworkInitialize()?

blackpuppy — Thu, 12 May 2005 03:43:12 GMT

Thanks, Fredrik and Brock!

I've tried and both methods work! As I need to toggle the culture for the whole web site instead of individual page, I prefer to do it in application's PreRequestHandlerExeute event handler.

Please refer to the help of HttpApplication Class.
An application executes events that are handled by modules or user code that is defined in the Global.asax file in the following sequence:
   1. BeginRequest
   2. AuthenticateRequest
   3. PostAuthenticateRequest
   4. AuthorizeRequest
   5. PostAuthorizeRequest
   6. ResolveRequestCache
      An event handler (a page corresponding to the request URL) is created at this point.
   7. PostResolveRequestCache
   8. PostMapRequestHandler
   9. AcquireRequestState
10. PostAcquireRequestState
11. PreRequestHandlerExecute
      The event handler is executed.
12. PostRequestHandlerExecute
13. ...

I tried BeginRequest, but it does not work. I guess the reason is that the Page.Request will be created later and will overwrite the thread culture set in BeginRequest.
Till 10. PostAcquireRequestState, the request is prepared, and only after that can we change the thread culture. Doing that in 11. PreRequestHandlerExecute is exactly Brock's approach.
"The event handler is executed." between 11 and 12 is the whole page's processing including any event handlers in the webform's codebehind, I think. Fredrik's approach, setting the thread culture in InitializeCulture is exactly here.

I still have one more problem. The toggle button's event handler will be executed after the thread culture is set (either in PreRequestHandlerExecute or in InitializeCulture). The result is that after the page reaches the browser the target culture will be different from the thread culture. While in any other events, since the target culture is not changed, the target culture will be the same as the thread culture. This is a inconsistent behavour. But it is not much a ASP.NET technical problem.

Thanks!
Zhu Ming

Re: Where to set/change page's culture prior to FrameworkInitialize()?

BrockAllen — Wed, 11 May 2005 16:09:34 GMT

Fredrik's approach works, but it's a PITA (IMO) if it's to be done on every page (or in a common base class). We just discussed this the other day, so it's an alternative for you:

http://forums.asp.net/920819/ShowPost.aspx

-Brock