Blazor 本地化的工作方式是否发生了变化？

Question

I've been trying to implement resource pages for both English and Norwegian in a Blazor serverside app. I have follow different guides with some different syntax ( Microsoft's guide and an article from c-sharpcorner ), but as you can see in the picture at the bottom it still says "welcome" (which is the keyword) when it should say "Hello.". I have the correct imports (according to the docs and guides) and here is my project structure:

Here is what Startup.cs looks like now:

namespace LocalizingTest
{
public class Startup
{
    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
    }

    public IConfiguration Configuration { get; }

    // This method gets called by the runtime. Use this method to add services to the container.
    // For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddLocalization(options => options.ResourcesPath = "Resources");
        var supportedCultures = new List<CultureInfo>
        {
            new CultureInfo("en-GB"), 
            new CultureInfo("nb")
        };
        services.Configure<RequestLocalizationOptions>(options => 
        {
            options.DefaultRequestCulture = new Microsoft.AspNetCore.Localization.RequestCulture("en-GB");
            options.SupportedUICultures = supportedCultures;
        });

        services.AddRazorPages();
        services.AddServerSideBlazor();
        services.AddSingleton<WeatherForecastService>();

    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }
        else
        {
            app.UseExceptionHandler("/Error");
            // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
            app.UseHsts();
        }

        app.UseRequestLocalization();

        app.UseHttpsRedirection();

        app.UseStaticFiles();

        app.UseRouting();

        app.UseEndpoints(endpoints =>
        {
            endpoints.MapBlazorHub();
            endpoints.MapFallbackToPage("/_Host");
        });
    }
}
}

And Counter.razor:

@page "/counter"

@inject IStringLocalizer<Counter> Translator

<h1>Counter</h1>

<p>Current count: @currentCount</p>

<p>@Translator["welcome"]</p>

<button class="btn btn-primary" @onclick="IncrementCount">Click me</button>

@code {
    private int currentCount = 0;

    private void IncrementCount()
    {
        currentCount++;
    }
}

I can't find any discrepancies between my project and those shown in tutorials/docs, so has anything changed with Blazor server-side localization, or am I missing something really obvious?

Answer 1

For others having the same issue. Don't forget to add RequestCultureProviders:

services.Configure<RequestLocalizationOptions>(options => 
        {
            options.DefaultRequestCulture = new Microsoft.AspNetCore.Localization.RequestCulture("en-GB");
            options.SupportedUICultures = supportedCultures;

            // <-- This
            options.RequestCultureProviders.Add(new AcceptLanguageHeaderRequestCultureProvider());
        });

AcceptLanguageHeaderRequestCultureProvider changes the culture base on the accept-language header. There are also other providers (see https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.localization.requestcultureprovider ).