UI Default texts not resolving in Azure App Service

[EliasIsmail]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

So, I recently upgraded from version 8.11.0 to 10.2.3.
I am using a Table component, as seen below:

<Table TItem="Foo" IsPagination="true" .....

When testing on my local machine, everything is working as expected. However, when I publish my service to run as an Azure App Service, the UI acts differently. It is as if certain default text values (i.e. unset parameters in the table component) cannot be resolved for buttons, filters etc - despite it working on my own machine. So it seems environment specific somehow, as the code is 1:1 the same.

I believe this began to happen right around version 9.x.x - which is why I have stayed on version 8.11.0 for some time. I know some of these text values can be set via parameters, and in the worst case I can re-implement some things manually - but I just wanted to make sure there isn't any obvious fix, before I spend a lot of time doing that.

Examples in Local Dev mode:

Table pagination:

Table filtering:

Examples in App Service / Published mode:

Table pagination:

Table filtering:

Kind regards

Expected Behavior

That the default text values are resolved to defaults, when not explicitly set - independently of the environment. For example, the page items showing the page size (number) instead of static PageItemText for each entry - despite using recommended PageItemsSource parameter.

Interactive render mode

Interactive Server (Interactive server-side rendering (interactive SSR) using Blazor Server)

Steps To Reproduce

Publish app service using version >= 9.x.x as Azure App Service, and notice default text strings

Exceptions (if any)

No response

.NET Version

NET8.0

Anything else?

Errors occur on hosted Azure App Service, but works on local machine - same exact code.

[bb-auto]

@EliasIsmail Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.

[ArgoZhang]

@EliasIsmail thank you for contacting us. let's check it and feedback later.

[ArgoZhang]

@EliasIsmail hi. Could you package and upload the BootstrapBlazor.dll file that has already been published on Azure here?

[EliasIsmail]

@EliasIsmail hi. Could you package and upload the BootstrapBlazor.dll file that has already been published on Azure here?

Hi Argo,

Yes, sure - I have downloaded the files from the App Service via FTPS and attached them here - the BootstrapBlazor.dll, BootstrapBlazor.FontAwesome.dll + BoostrapBlazor.PdfViewer.dll (if should be required). Version is 10.3.0 (latest). Download link via file.io / Limewire below:

https://limewire.com/d/M4vsi#GgDaXm5kGA

Additional information:
I tested the case for v9.0.0 earlier today, and there were no errors there. Then upgraded to 10.3.0, and the issue reappeared (attached files) - so somewhere between those 2 versions.

[ArgoZhang]

@EliasIsmail Thank you so much! I'll check each version one by one and find and fix the problem as soon as possible.

[EliasIsmail]

@EliasIsmail Thank you so much! I'll check each version one by one and find and fix the problem as soon as possible.

Hi Argo,

Thank you! Let me know if I can do anything.

[ArgoZhang]

@EliasIsmail I checked the resource files in the DLL file using a tool, and they appear to be fine.

Could you create a simple project to reproduce the issue, and then package all the publish files and send them to me so I can reproduce it?

BTW Could you also please provide me with the Azure App Service address?

[EliasIsmail]

@EliasIsmail I checked the resource files in the DLL file using a tool, and they appear to be fine.

Could you create a simple project to reproduce the issue, and then package all the publish files and send them to me so I can reproduce it?

BTW Could you also please provide me with the Azure App Service address?

Using your attached picture, it made me think that it is likely something with how Azure App Service interprets the culture info somehow. So I tried setting the DefaultCultureInfo (and FallbackCulture) in code:

builder.Services.AddBootstrapBlazor(configOptions => { configOptions.DefaultCultureInfo = "en"; configOptions.FallbackCulture = "en-US"; }, null);

And it worked. Which is a completely fine 'work-around' for me.
So it might just be something particular with Azure App Service handling the cultureinfo, that requires it to be set as default.

[densen2014]

Please try editing the configuration file appsettings.json ...

{
   
  "BootstrapBlazorOptions": {
    "ToastDelay": 4000,
    "MessageDelay": 4000,
    "SwalDelay": 4000,
    "EnableErrorLogger": true,
    "FallbackCulture": "es",
    "SupportedCultures": [
      "es-ES",
      "zh-CN",
      "en-US"
    ],
    "TableSettings": {
      "CheckboxColumnWidth": 36,
      "ColumnMinWidth": 80,
      "TableExportOptions": {
        "EnableFormat": false,
        "EnableLookup": true,
        "AutoMergeArray": true,
        "ArrayDelimiter": ","
      }
    },
    "IgnoreLocalizerMissing": true,
    "StepSettings": {
      "Short": "1",
      "Int": "1",
      "Long": "1",
      "Float": "0.1",
      "Double": "0.01",
      "Decimal": "0.01"
    },
    "DefaultCultureInfo": "es-ES" 
  }
}

or try

        var cultureInfo = new CultureInfo("es"); 
        cultureInfo.NumberFormat.CurrencySymbol = "€";
        ...
        CultureInfo.DefaultThreadCurrentCulture = cultureInfo;
        CultureInfo.DefaultThreadCurrentUICulture = cultureInfo;