在Startup ConfigureServices 注冊本地化所需要的服務AddLocalization和 Configure<RequestLocalizationOptions>
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
public void ConfigureServices(IServiceCollection services) { services.AddLocalization(); services.Configure<RequestLocalizationOptions>(options => { var supportedCultures = new List<CultureInfo> { new CultureInfo("en-us"), new CultureInfo("zh-cn") }; options.DefaultRequestCulture = new RequestCulture(culture: "en-us", uiCulture: "en-us"); options.SupportedCultures = supportedCultures; options.SupportedUICultures = supportedCultures; options.RequestCultureProviders = new IRequestCultureProvider[] { new RouteDataRequestCultureProvider { IndexOfCulture = 1, IndexofUiCulture = 1 } }; }); services.Configure<RouteOptions>(options => { options.ConstraintMap.Add("culture", typeof(LanguageRouteConstraint)); }); services.AddControllers(); } |
在Startup.cs類的Configure 方法中添加請求本地化中間件。
|
1
2
|
var localizeOptions = app.ApplicationServices.GetService<IOptions<RequestLocalizationOptions>>(); app.UseRequestLocalization(localizeOptions.Value); |
RequestCultureProvider 它使用簡單的委托來確定當前的本地化區域性，當然我們還可以通過RequestCultureProvider自定義源的請求區域信息比如說配置文件或者數據庫都是可以的.或者說我們可以選用默認的一些方式讓我們去獲取到當前區域.
ASP.NET Core 本地化默認向我們提供了四個方式，可用于確定正在執行的請求的當前區域性：
- QueryStringRequestCultureProvider
- CookieRequestCultureProvider
- AcceptLanguageHeaderRequestCultureProvider
- CustomRequestCultureProvider
如下所示我將通過路由的方式,去確定當前區域
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
public class RouteDataRequestCultureProvider : RequestCultureProvider { public int IndexOfCulture; public int IndexofUiCulture; public override Task<ProviderCultureResult> DetermineProviderCultureResult(HttpContext httpContext) { if (httpContext == null) throw new ArgumentNullException(nameof(httpContext)); string uiCulture; string culture = uiCulture = httpContext.Request.Path.Value.Split('/')[IndexOfCulture]; var providerResultCulture = new ProviderCultureResult(culture, uiCulture); return Task.FromResult(providerResultCulture); } } |
通過如下代碼片段實現IRouteConstraint對路由做相應的約束
|
1
2
3
4
5
6
7
8
9
10
11
12
|
public class LanguageRouteConstraint : IRouteConstraint{ public bool Match(HttpContext httpContext, IRouter route, string routeKey, RouteValueDictionary values, RouteDirection routeDirection) { if (!values.ContainsKey("culture")) return false; var culture = values["culture"].ToString(); return culture == "en-us" || culture == "zh-cn"; }} |
添加區域資源文件
注入IStringLocalizer<T>，StringLocalizer將通過傳遞的共享資源(T)的值映射到資源文件,然后將本地化根據字符串的名稱從資源文件返回響應的值
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
[Route("{culture:culture}/[controller]")][ApiController]public class HomeController : ControllerBase{ private readonly IStringLocalizer<Resource> localizer; public HomeController(IStringLocalizer<Resource> localizer) { this.localizer = localizer; } public string Get() { return localizer["Home"]; }} |
如下圖所示
Reference
https://github.com/hueifeng/BlogSample/tree/master/src/LocalizationSingleResx
到此這篇關于ASP.NET Core WebAPI實現本地化(單資源文件)的文章就介紹到這了,更多相關ASP.NET Core WebAPI本地化內容請搜索服務器之家以前的文章或繼續瀏覽下面的相關文章希望大家以后多多支持服務器之家！
原文鏈接：https://www.cnblogs.com/yyfh/p/12995208.html
