Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR

C-Jesse Bryan 0

I have a Blazor interactive server side .net 8 application. I wanted to change the default DateTimeFormat across the entire application for certain Cultures, so I created some custom CultureInfo's shown here:

public static List<CultureInfo> CustomCultures { get; set; } = new List<CultureInfo>()
{
    new CultureInfo("en-US", false) { DateTimeFormat = { ShortDatePattern = "MM/dd/yyyy" } },
    new CultureInfo("fr-CA", false) { DateTimeFormat = { ShortDatePattern = "yyyy-MM-dd" } }
};

I then added those cultures to our supported cultures in Program.cs

public static void AddPortalLocalization(this WebApplicationBuilder builder)

{
    builder.Services.Configure<RequestLocalizationOptions>(options =>
    {
        var supportedCultures = CommonConstantsAndReadOnlys.CustomCultures;
        options.DefaultRequestCulture = new RequestCulture(CommonConstantsAndReadOnlys.CustomCultures.First());
        options.SupportedCultures = supportedCultures;
        options.SupportedUICultures = supportedCultures;
    });
    builder.Services.AddLocalization();
}

I also have a dropdown selector in the application which lets users choose their culture, and it adds a cookie to the browser:

public IActionResult SetCulture(string cultureName, string redirectUri)
{
    var customCulture = CommonConstantsAndReadOnlys.CustomCultures.FirstOrDefault(c => c.Name == cultureName);
    if (customCulture != null)
    {
        HttpContext.Response.Cookies.Append(
            CookieRequestCultureProvider.DefaultCookieName,
            CookieRequestCultureProvider.MakeCookieValue(new RequestCulture(customCulture)));
    }
    return LocalRedirect(redirectUri);
}

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. I am using AzureSignalR and set it up in Program.cs as shown here:

public static void ConfigureSharedSignalR(
   this WebApplicationBuilder builder,
    string? connectionString = null)
{
    connectionString = string.IsNullOrWhiteSpace(connectionString) ?
        builder.Configuration.GetConnectionString("SharedSignalR") : connectionString;
    builder.Services.AddSignalR().AddAzureSignalR(connectionString);
}

When I remove

.AddAzureSignalR(connectionString);

the custom cultures that I want to use work correctly and don't get overridden. Why does adding AzureSignalR override my custom cultures?
Also, is there a better/easier way to set my own default DateTimeFormat's that don't use CultureInfo across the application?

JasonPan - MSFT 4,791 Microsoft Vendor

Hi @C-Jesse Bryan,

How about using JSRuntime.InvokeVoidAsync, instead of API controller. Here is my sample code. And I can see date format correctly in my side.

@page "/culture-selector"
@inject NavigationManager Navigation
@inject IJSRuntime JSRuntime
@using System.Globalization
<h3>Select Culture</h3>
<select @onchange="SetCulture">
    @foreach (var culture in CommonConstantsAndReadOnlys.CustomCultures)
    {
        <option value="@culture.Name">@culture.DisplayName</option>
    }
</select>
<h3>Current Date</h3>
<p>@formattedDate</p>
@code {
    private string formattedDate;
    protected override void OnInitialized()
    {
        var currentCulture = CultureInfo.CurrentCulture;
        formattedDate = DateTime.Now.ToString(currentCulture.DateTimeFormat.ShortDatePattern);
    }
    private async Task SetCulture(ChangeEventArgs e)
    {
        var cultureName = e.Value.ToString();
        var customCulture = CommonConstantsAndReadOnlys.CustomCultures.FirstOrDefault(c => c.Name == cultureName);
        if (customCulture != null)
        {
            await JSRuntime.InvokeVoidAsync("setCulture", customCulture.Name);
            Navigation.NavigateTo(Navigation.Uri, forceLoad: true);
        }
    }
}

Best Regards

Jason

C-Jesse Bryan 0 Reputation points

2024-06-26T22:32:19.7566667+00:00

Hi Jason, thanks for the reply.

Did you try it in conjunction with using AzureSignalR? I tried using JSInterop, and that works similarly to how the CultureController is working. It shows the correct date time format for a half second before returning to the default format.
JasonPan - MSFT 4,791 Reputation points Microsoft Vendor

2024-06-27T04:11:48.61+00:00

Hi @C-Jesse Bryan,

Yes, I'm using Azure SinalR, and it's possible that my sample code doesn't reproduce your scenario correctly. Would you mind creating a new repo for us so we can investigate this issue?

And please hide you sensitive information too, thanks for your understanding.

Best Regards

Jason
C-Jesse Bryan 0 Reputation points

2024-07-02T01:27:18.0933333+00:00

Hi Jason, sorry for the delay. I have created a very simple repo here:

https://github.com/jbryanSavers/BlazorCultureCookieSignalRTest

This is basically just the default Blazor Web App, with some changes to App.razor, Home.razor, and Program.cs. I removed the culture changer for simplicity, and just set a default culture that uses my specified date time format and hooked up AzureSignalR. When you put in a connection string, you'll see the datetimeformat starts correct (MM/dd/yyyy) for half a second before changing to M/d/yyy. Hopefully this helps, and there is something obvious that I'm doing incorrectly.
JasonPan - MSFT 4,791 Reputation points Microsoft Vendor

2024-07-02T02:22:23.2766667+00:00

Hi @C-Jesse Bryan,

Thanks for your sharing. I've escalated the issue internally, please be patient.

In addition, this thread has a low priority, please be patient and wait for our reply.

Best Regards

Jason
David Thielen 2,506 Reputation points

2024-07-02T16:16:03.28+00:00

off-topic curiosity question - what does builder.Services.AddSignalR().AddAzureSignalR(connectionString); do?

thanks - dave

Share via

Blazor Server Side Custom CultureInfo getting overridden when using AzureSignalR