Localization for async calls in ASP.NET WebApi

Question

Hi– I'm planning to handle server side localization for error strings etc. based on the “Accept-Language” header, by setting the CurrentUICulture based on that header, but apparently it doesn’t flow though the async calls, below is a sample code to illustrate the problem, is there any default way of handling the localization for async calls?

   public async Task<HttpResponseMessage> GetAsync()
    {            
        //set the current ui culture, to say "fr-FR", based on "Accept-Language" header
        Thread.CurrentThread.CurrentUICulture = CultureInfo.GetCultureInfo("**fr-FR**");  

       var task = httpClient.PutAsync(endpoint, content)            

        //do some processing

        var res  = await task;

        var culture = Thread.CurrentThread.CurrentUICulture.Name; **//ITS NOT necessarily fr-FR**

        //do some more processing
        //and handle localizations etc.

        return res;
    }

I'm looking for a cleaner/seamless way of handling localization for cases where there are real async operations esp. for the code following the await call

Edit: replaced Task.Run() with httpClient.PutAsync for clarity

Darin Dimitrov · Accepted Answer · 2012-12-31 09:09:46Z

2

Task.Run and Task.Factory.StartNew do not have any context. That's an expected behavior. Context is preserved when you use the await keyword. So here's what you could do:

public static async Task<IEnumerable<string>> GetAsync()
{            
    //set the current ui culture, to say "fr-FR", based on "Accept-Language" header
    Thread.CurrentThread.CurrentUICulture = CultureInfo.GetCultureInfo("fr-FR");

    //do some processing

    var s = await GetSomething();

    var culture = Thread.CurrentThread.CurrentUICulture.Name; //It's ja-JP

    return new[] { s, s };
}

public static Task<string> GetSomething()
{
    var cuture = Thread.CurrentThread.CurrentUICulture.Name; // It's fr-FR
    var tcs = new TaskCompletionSource<string>();
    Thread.CurrentThread.CurrentUICulture = CultureInfo.GetCultureInfo("ja-JP");
    tcs.SetResult("<something>");
    return tcs.Task;
}

answered Dec 31, 2012 at 9:09

Darin Dimitrov

1.0m277 gold badges3.3k silver badges3k bronze badges

Sign up to request clarification or add additional context in comments.

15 Comments

user1929044 Over a year ago

It's not guaranteed as the 3 parts (1. GetSomething() call 2. the code before and 3. the code after it) can potentially run on 3 different asp.net threads esp. if GetSomething() is a long running async operation.

Darin Dimitrov Over a year ago

If you are using the code in my example, they will run on the same context. If you create tasks with Task.Run or Task.Factory.StartNew they are not guaranteed to run on the same thread.

user1929044 Over a year ago

I'm looking for a cleaner/seamless way of handling localization for cases where there are real async operations like calls to another webservice etc, by default, the context won't be the same for such cases.

user1929044 Over a year ago

yes but when it returns, the remaining part can potentially execute on a 3rd thread not necessarily on the original thread

user1929044 Over a year ago

The sample given in the question sets the current ui culture, to say "fr-FR", based on "Accept-Language" header before the await call, one approach is we can set the current ui culture again after each await call, to say "fr-FR", based on "Accept-Language" header. The ask was if this can be done in a seamless way, looks like that's not possible. Anyways, thanks Darin for the prompt responses.

|

Collectives™ on Stack Overflow

Localization for async calls in ASP.NET WebApi

1 Answer 1

15 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

15 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related