Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR #2038

Open
DillionVVV opened this issue Sep 6, 2024 · 1 comment · Fixed by #2067 · May be fixed by #2068
Open

Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR #2038

DillionVVV opened this issue Sep 6, 2024 · 1 comment · Fixed by #2067 · May be fixed by #2068
Assignees

Comments

@DillionVVV
Copy link

Describe the bug

I notice when running the application it uses my custom culture for half a second, then updates and goes back to the default CultureInfo properties for whatever culture i'm using.
the custom cultures that I want to use work correctly and don't get overridden. Why does adding AzureSignalR override my custom cultures?

More detail information, see Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR.

To Reproduce

Repo:
https://github.com/jbryanSavers/BlazorCultureCookieSignalRTest

Without using Azure-SignalR, the output:

image

Using Azure-SignalR, the result like this:

image

Exceptions (if any)

Further technical details

  • Your Azure SignalR SDK version: Using Latest Version .

  • Your Server ASPNETCORE version or Assembly version of Microsoft.AspNetCore.SignalR

  • Your SignalR Client SDK version

@xingsy97 xingsy97 self-assigned this Sep 6, 2024
@xingsy97
Copy link
Contributor

xingsy97 commented Sep 6, 2024

I'll investigate this culture bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants