Missing info about flag that controls WPF's Dispatcher Culture behavior

[pawlos]

Type of issue

Other (describe below)

Description

I was debugging an issues we had in WPF project after migrating from 4.5 to 4.8 that resulted in application language switching not working correctly. During the debugging, CurrentCulture and CurrentUICulture on System.Threading.CurrentThread were constantly switching back and forth between the new language and the old one.

After debugging discovered there's a flag Switch.MS.Internal.DoNotUseCulturePreservingDispatcherOperations that reverts back the behavior to the old one, but couldn't find it documented in the docs. I only found some mentioned of it in PRs, issues and in code. It would be nice to have it documented so that other doesn't have to the debugging.

Finally we had to also set the flag NoAsyncCurrentCulture which is mentioned in this doc so I'm wondering why the other one is not. Is there any reason this flag is not documented?

Page URL

https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/retargeting/4.6.x

Content source URL

https://github.com/dotnet/docs/blob/live/docs/framework/migration-guide/retargeting/4.6.x.md

Document Version Independent Id

7f031ebd-29b8-2ab5-9630-ffb11838515c

Article author

@gewarren

Metadata

• ID: cce538cd-8550-f948-cdaa-569c26449a20
• Service: dotnet-framework
• Sub-service: app-compat

[kirides]

We had to enable BOTH options to be able to fetch user language preferences at runtime before "Show"-ing the first window.
As the fetching occurs asynchronously the dispatcher and Tasks always overrode the CultureInfo settings back to the "default".

But WPF required us to properly set CultureInfo.CurrentUICulture as binding otherwise used wrong resources (x:Static SomeResource.Text or ToString()-based bindings)