Bu makale i\u00e7erisinde ise\u00a0ASP.NET Core MVC<\/strong> ve Elasticsearch <\/strong>i\u00e7erisinde, nas\u0131l “globalization<\/em>” deste\u011fini sa\u011flayabiliriz konusuna de\u011finmeye \u00e7al\u0131\u015faca\u011f\u0131m.<\/p>\n Globalization konusunun \u00f6nemiyle alakal\u0131 k\u00fc\u00e7\u00fck bir giri\u015f yapman\u0131n ard\u0131ndan, ASP.NET Core<\/em>\u00a0MVC<\/em> i\u00e7erisinde globalization i\u015flemlerini nas\u0131l ger\u00e7ekle\u015ftirebiliriz konusuna \u00f6ncelikle bir bakal\u0131m. Globalization konusunda ASP.NET Core<\/em>, bize farkl\u0131 “dil” ve “culture” bilgileri i\u00e7in localization i\u015flemlerini ger\u00e7ekle\u015ftirebilmemiz ad\u0131na middleware ve servisler sunmaktad\u0131r.<\/p>\n Localization i\u015flemini ger\u00e7ekle\u015ftirebilmek i\u00e7in uygulayaca\u011f\u0131m\u0131z \u00fc\u00e7 temel nokta bulunmaktad\u0131r:<\/p>\n Bu noktalardan yola \u00e7\u0131karak, uygulaman\u0131n content’ini nas\u0131l localizable bir hale getirebiliriz konusuna bir bakal\u0131m.<\/p>\n NOT<\/strong>: \u00d6rnekler i\u00e7in “ASP.NET Core Web App (Model-View-Controller)<\/em>” template’ini kullanaca\u011f\u0131m. “dotnet new mvc<\/em>“<\/p><\/blockquote>\n Asl\u0131nda,\u00a0ASP.NET<\/strong> deki “.resx<\/em>” resource dosyalar\u0131 ile benzerlik g\u00f6stermektedir. Hat\u0131rlarsak uygulama i\u00e7erisinde desteklenen her bir culture bilgisi i\u00e7in bir “.resx<\/em>” resource dosyas\u0131 ekliyorduk. Ard\u0131ndan ise “Resources.Name<\/em>” \u015feklinde eri\u015fim sa\u011flayarak, culture bilgisine uygun olan localize edilmi\u015f content’i kullan\u0131yorduk.<\/p>\n ASP.NET Core<\/em> i\u00e7erisinde ise localize edilmi\u015f content’i alabilmek i\u00e7in “Resources.Name<\/em>” yakla\u015f\u0131m\u0131 yerine, “IStringLocalizer<\/strong>” ve “IStringLocalizer<\/strong>” tipinde iki adet abstraction bulunmaktad\u0131r.<\/p>\n \u00d6rne\u011fin:<\/p>\n Localizer’\u0131n kullan\u0131m\u0131na dikkat ettiniz mi? Localizer’\u0131n i\u00e7erisine bir key set etmek yerine, bir content set ettik. ASP.NET Core<\/em> i\u00e7erisindeki en b\u00fcy\u00fck fark ise, istenilen culture bilgisi i\u00e7in localize bir content bulunamaz ise, i\u00e7erisine set edilen content’i resource olarak kullanmaktad\u0131r. Bu sayede main culture bilgisi i\u00e7in bir resource dosyas\u0131 olu\u015fturmaya gerek kalmamaktad\u0131r. Tabi code review’lar s\u0131ras\u0131nda magic string’lere<\/strong> tak\u0131nt\u0131l\u0131 biri olarak, bu durumdan pek ho\u015fland\u0131\u011f\u0131m\u0131 s\u00f6yleyemem. :)<\/p>\n NOT<\/strong>: HTML<\/em> i\u00e7eren content’ler i\u00e7in ise, “IHtmlLocalizer<\/em>” ve “IHtmlLocalizer<\/em>” tipleri de bulunmaktad\u0131r.<\/p><\/blockquote>\n Farkl\u0131 tiplerdeki localizer’lara eri\u015febilmek i\u00e7in ise birde “IStringLocalizerFactory<\/strong>” bulunmaktad\u0131r.<\/p>\n \u00d6rne\u011fin shared resource’lara eri\u015febilmek i\u00e7in, a\u015fa\u011f\u0131daki gibi kullanabilmekteyiz.<\/p>\n Factory \u00fczerinde bulunan “Create<\/em>” method’u ile, istenilen resource i\u00e7in bir localizer olu\u015fturabiliriz.<\/p>\n View localization k\u0131sm\u0131na bakt\u0131\u011f\u0131m\u0131zda ise,\u00a0servis olarak kullanabilece\u011fimiz\u00a0“IViewLocalizer<\/strong>” bulunmaktad\u0131r. “ViewLocalizer<\/em>” ise “IHtmlLocalizer<\/em>” \u0131 implemente etmektedir. Bu noktada Razor<\/em>, parametreler hari\u00e7 localize edilmi\u015f string’i HTML<\/em> encode yapmamaktad\u0131r.<\/p>\n \u00d6rnek bir view’a bakal\u0131m:<\/p>\n Yukar\u0131daki localize edilmi\u015f string’in \u00e7\u0131kt\u0131s\u0131, a\u015fa\u011f\u0131daki gibi olacakt\u0131r.<\/p>\n \u00c7\u0131kt\u0131ya bakt\u0131\u011f\u0131m\u0131zda ise Razor<\/em>‘\u0131n, parametre de\u011ferleri hari\u00e7 localize edilmi\u015f string’i\u00a0HTML<\/em> encode yapmad\u0131\u011f\u0131n\u0131 g\u00f6rmekteyiz.<\/p>\n View’lar\u0131 en basit haliyle nas\u0131l localize edebilece\u011fimizi g\u00f6rd\u00fck. \u015eimdi birde\u00a0Data Annotations<\/strong>‘lar\u0131n localization konusuna bir bakal\u0131m. Bu noktada ise yine i\u015fimiz gayet basittir. ASP.NET Core<\/em> i\u00e7erisinde data annotations’lar hali haz\u0131rda “IStringLocalizer<T><<\/strong>” ile localize edilmi\u015f durumdad\u0131r.<\/p>\n \u00d6rne\u011fin:<\/p>\n Yukar\u0131daki gibi bir kullan\u0131mda “This field is required.<\/em>” ve “Name<\/em>” string’leri, istenilen culture’da bir resource dosyas\u0131 varsa bu de\u011ferler localize edilecektir.<\/p>\n Asl\u0131nda makalenin giri\u015finde de bahsetti\u011fim gibi localize edilmi\u015f resource dosyalar\u0131, ASP.NET<\/em>‘deki “.resx<\/em>” resource dosyalar\u0131 ile ayn\u0131d\u0131r. Visual Studio<\/em> \u00fczerinden, a\u015fa\u011f\u0131daki gibi ekleyebilmekteyiz.<\/p>\n NOT<\/strong>: Hen\u00fcz Visual Studio Code<\/em> ve Visual Studio for MAC<\/em> \u00fczerinden eklenememektedir. :(<\/p><\/blockquote>\n Bu noktada dikkat etmemiz gereken \u00f6nemli unsurlardan birisi, resource dosyalar\u0131n\u0131n isimlendirilmesidir.<\/p>\n Hem class’lar\u0131n hem de view’lar\u0131n i\u00e7erisinde kullanm\u0131\u015f oldu\u011fumuz localizer’lar, iki farkl\u0131 y\u00f6ntemle localize edilmi\u015f resource’lara eri\u015fim sa\u011flamaktad\u0131r.<\/p>\n Buradaki kullan\u0131m tercihi tamamen bize kalm\u0131\u015f durumdad\u0131r.<\/p>\n Bu noktaya kadar content’leri nas\u0131l localize bir hale getirebiliriz konular\u0131na bakt\u0131k. \u015eimdi ise localization servislerini, uygulama i\u00e7erisine nas\u0131l ekleyebiliriz ve configure edebiliriz k\u0131s\u0131mlar\u0131na de\u011finece\u011fiz.<\/p>\n \u0130lk olarak resource dosyalar\u0131 i\u00e7in olan path’i,\u00a0Startup<\/em> class’\u0131 i\u00e7erisinde a\u015fa\u011f\u0131daki gibi belirleyebilmek m\u00fcmk\u00fcnd\u00fcr.<\/p>\n NOT<\/strong>: E\u011fer herhangi bir path set etmez isek, localization servisi culture resource’lar\u0131n\u0131 uygulaman\u0131n root folder’\u0131 alt\u0131nda arayacakt\u0131r.<\/p><\/blockquote>\n View’lar i\u00e7in localization’\u0131 etkinle\u015ftirebilmek ise localization servisini a\u015fa\u011f\u0131daki gibi service collection’\u0131na ekleyebiliriz.<\/p>\n E\u011fer resource dosyalar\u0131 olu\u015fturmak yerine culture’lara g\u00f6re farkl\u0131 view’lar olu\u015fturmak istersek, “LanguageViewLocationExpanderFormat<\/em>” parametresi ile m\u00fcmk\u00fcnd\u00fcr.<\/p>\n “LanguageViewLocationExpanderFormat<\/em>” enum’\u0131, “SubFolder<\/em>” ve “Suffix<\/em>” de\u011ferlerine sahiptir.<\/p>\n Data annotation’lar i\u00e7in ise localization’\u0131, “AddDataAnnotationsLocalization<\/em>” method’u sa\u011flayabiliriz:<\/p>\n Data annotation’lar i\u00e7in shared bir resource kullanmak istiyorsak e\u011fer, a\u015fa\u011f\u0131daki gibi configure etmemiz yeterli olacakt\u0131r.<\/p>\n “Configure<\/em>” method’u i\u00e7erisinde eklememiz gereken bir di\u011fer \u00f6nemli middleware ise, Request Localization<\/strong> middleware’idir.<\/p>\n Burada uygulaman\u0131n destekleyece\u011fi culture bilgilerini ve default culture bilgisini belirleyebiliriz.<\/p>\n Localization’\u0131n son k\u0131sm\u0131 olarak implementasyon stratejilerine bakaca\u011f\u0131z. Request localization middleware’i, current culture’\u0131 se\u00e7ebilmek i\u00e7in default olarak \u00fc\u00e7 farkl\u0131 opsiyona sahiptir.<\/p>\n Opsiyonel olarak kullanabilece\u011fimiz birde, “RouteDataRequestCultureProvider<\/strong>” vard\u0131r. Bununla birlikte route \u00fczerinden\u00a0localize edebilmek m\u00fcmk\u00fcnd\u00fcr. \u00d6rne\u011fin:\u00a0“http:\/\/localhost:5000\/en-US\/home<\/em>”<\/p>\n Bunun i\u00e7in:<\/p>\n Yukar\u0131daki kod blo\u011funa bakt\u0131\u011f\u0131m\u0131zda “MapMiddlewareRoute<\/em>” method’u ile culture bilgisini, localization middleware’i \u00e7al\u0131\u015fmadan \u00f6nce yakal\u0131yoruz. Bunu yapmam\u0131z\u0131n sebebi ise, localization middleware’inin\u00a0MVC<\/em> router’\u0131ndan \u00f6nce \u00e7al\u0131\u015f\u0131yor olmas\u0131d\u0131r. Ard\u0131ndan “RouteDataRequestCultureProvider<\/em>” \u0131 ilk request culture provider’\u0131 olarak insert ederek, request localization middleware’ini configure ettik. Son olarak route template’i i\u00e7erisine ise birde culture bilgisini ekledik. Bu configuration ile, localization i\u015flemi route \u00fczerinden gelen culture bilgisi ile ger\u00e7ekle\u015ftirilecektir.<\/p>\n NOT<\/strong>: Bu implementasyonlar\u0131 i\u00e7eren bir \u00f6rne\u011fi, makalenin sonunda payla\u015f\u0131yor olaca\u011f\u0131m.<\/p><\/blockquote>\n Elasticsearch<\/em> k\u0131sm\u0131nda ise her bir culture bilgisi i\u00e7in, farkl\u0131 index’ler<\/strong> olu\u015fturarak multi-language deste\u011fini sa\u011flayaca\u011f\u0131z. Burada tercih edebilece\u011finiz farkl\u0131 y\u00f6ntemlerde mevcut. \u00d6rne\u011fin tek bir index \u00fczerinde multi-field’lar ile multi-language deste\u011fini sa\u011flayabilmek gibi. Farkl\u0131 index’ler olu\u015fturarak multi-language deste\u011fi sa\u011flamak, ileride farkl\u0131 culture bilgilerinin de kolayl\u0131kla entegre olabilmesi a\u00e7\u0131s\u0131ndan kolayl\u0131k sa\u011flayacakt\u0131r. Buna ek olarak her bir dil bilgisi i\u00e7in analyzer’lar ayarlayabilmek de kolay olacakt\u0131r. (Ben daha \u00f6nce bu \u015fekilde kulland\u0131m)<\/p>\n \u00d6rnek i\u00e7erisinde ASP.NET Core MVC i\u00e7erisinde NEST<\/em> k\u00fct\u00fcphanesinin implementasyonunu ger\u00e7ekle\u015ftirece\u011fiz. \u00d6ncelikle “IProductService<\/em>” isminde bir interface tan\u0131mlayal\u0131m.<\/p>\n “CreateIndexAsync<\/em>” method’u ile bir index olu\u015fturup, “IndexAsync<\/em>” method’u ile de product’lar\u0131 indexleyece\u011fiz. Ard\u0131ndan kullan\u0131c\u0131n\u0131n istedi\u011fi culture bilgisine g\u00f6re ise search i\u015flemini “SearchAsync” method’u ile ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n \u015eimdi “ProductService<\/em>” isminde bir class olu\u015ftural\u0131m ve a\u015fa\u011f\u0131daki gibi implemente edelim.<\/p>\n “IndexAsync<\/em>” method’u ile “products_{langCode}<\/em>” \u015feklinde bir index name olu\u015fturduk ve product’lar\u0131 bu index name ile indexleyece\u011fiz. “SearchAsync<\/em>” method’u ile ise, istenilen dil bilgisine g\u00f6re “Name<\/em>” ve “Description<\/em>” field’lar\u0131 \u00fczerinde full text search i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n \u00d6rnek olarak a\u015fa\u011f\u0131daki gibi bir controller olu\u015ftural\u0131m.<\/p>\n Controller’\u0131n “Index<\/em>” method’u i\u00e7erisinde T\u00fcrk\u00e7e<\/strong> ve \u0130ngilizce<\/strong> culture’lar\u0131 i\u00e7in bir index olu\u015fturaca\u011f\u0131z ve product’lar\u0131 olu\u015fturulan bu index’e feed edece\u011fiz. “Products<\/em>” action i\u00e7erisinde ise query string \u00fczerinden alacak oldu\u011fumuz “keyword<\/em>” ile, culture’a uygun product index’i \u00fczerinden search i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n “Products<\/em>” action i\u00e7in ise a\u015fa\u011f\u0131daki gibi bir view olu\u015ftural\u0131m.<\/p>\n Docker<\/em> \u00fczerinde test i\u015flemleri i\u00e7in single-node olarak bir\u00a0Elasticsearch<\/em>\u00a0\u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n Son olarak “Startup<\/em>” class’\u0131 i\u00e7erisinde ise, “ProductService<\/em>” ve “ConnectionSettings<\/em>” class’lar\u0131n\u0131n service collection’\u0131na injection i\u015flemini a\u015fa\u011f\u0131daki gibi ger\u00e7ekle\u015ftirelim.<\/p>\n \u0130\u015fte bu kadar.<\/p>\n \u015eimdi projeyi “dotnet run<\/em>” komut sat\u0131r\u0131 ile \u00e7al\u0131\u015ft\u0131ral\u0131m. Ard\u0131ndan\u00a0“http:\/\/localhost:5000\/tr-TR\/home<\/em>” URL’ine girelim. B\u00f6ylece product index’i olu\u015fturulacak ve product dok\u00fcmanlar\u0131 indexlenecektir.<\/p>\n \u015eimdi search i\u015flemi i\u00e7in “http:\/\/localhost:5000\/tr-TR\/home\/products?keyword=Cep Telefonu<\/em>” URL’ine browser \u00fczerinden girelim ve sonucuna bakal\u0131m.<\/p>\n E\u011fer response’a bakarsak,\u00a0resource’lar\u0131n culture’a g\u00f6re localize edildi\u011fini, ayr\u0131ca product result’lar\u0131n\u0131n da “products_tr<\/em>” index’i i\u00e7erisinde arand\u0131\u011f\u0131n\u0131 g\u00f6rebiliriz.<\/p>\n Culture bilgisini birde “en-US<\/em>“, keyword’\u00fc ise “Cell Phone<\/em>” olarak de\u011fi\u015ftirelim ve response’a tekrar bir bakal\u0131m. URL ise: “http:\/\/localhost:5000\/en-US\/home\/products?keyword=Cell Phone<\/em>“.<\/p>\n![\"\"](\"\/wp-content\/uploads\/2017\/12\/topic-globalization.jpg\")
<\/a><\/p>\n1) ASP.NET Core MVC’de Globalization<\/h4>\n
\n
1) Uygulaman\u0131n Content’ini Localizable Bir Hale Getirmek<\/h5>\n
public class TodoController : Controller\r\n{\r\n private readonly IStringLocalizer<TodoController> _localizer;\r\n\r\n public TodoController(IStringLocalizer<TodoController> localizer)\r\n {\r\n _localizer = localizer;\r\n }\r\n\r\n public IActionResult Index()\r\n {\r\n string hello = _localizer[\"Hello!\"];\r\n\r\n return View(hello);\r\n }\r\n}<\/pre>\npublic class TodoController : Controller\r\n{\r\n private readonly IStringLocalizer _localizerForShared;\r\n\r\n public CulturesController(IStringLocalizerFactory localizerFactory)\r\n {\r\n _localizerForShared = localizerFactory.Create(typeof(SharedResource));\r\n\r\n }\r\n}<\/pre>\n@using Microsoft.AspNetCore.Mvc.Localization\r\n\r\n@inject IViewLocalizer Localizer\r\n\r\n@Localizer[\"<h1>Selam {0}<\/h1>\", \"<b>G\u00f6khan<\/b>\"]<\/pre>\n<\/a><\/p>\npublic class TodoModel\r\n{\r\n [Required(ErrorMessage = \"This field is required.\")]\r\n [Display(Name = \"Name\")]\r\n public string Name { get; set; }\r\n}<\/pre>\n2) Localize Edilmi\u015f Resource Dosyas\u0131 Olu\u015fturmak<\/h5>\n
<\/a><\/p>\n\n
3) Configurasyon ve Implementasyon Stratejisi<\/h5>\n
public void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddLocalization(options => {\r\n options.ResourcesPath = \"Resources\";\r\n });\r\n}<\/pre>\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddMvc()\r\n .AddViewLocalization()\r\n}<\/pre>\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddMvc()\r\n .AddViewLocalization(LanguageViewLocationExpanderFormat.Suffix)\r\n}<\/pre>\n\n
public void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddMvc()\r\n .AddDataAnnotationsLocalization();\r\n}<\/pre>\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddMvc()\r\n .AddDataAnnotationsLocalization(options =>\r\n {\r\n options.DataAnnotationLocalizerProvider = (type, factory) => {\r\n return factory.Create(typeof(SharedResource));\r\n }\r\n });\r\n}\r\n\r\npublic class SharedResource\r\n{\r\n}<\/pre>\npublic void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n{\r\n var supportedCultures = new List\r\n {\r\n new CultureInfo(\"tr-TR\"),\r\n new CultureInfo(\"en-US\"),\r\n };\r\n\r\n app.UseRequestLocalization(new RequestLocalizationOptions\r\n {\r\n DefaultRequestCulture = new RequestCulture(\"tr-TR\"),\r\n SupportedCultures = supportedCultures,\r\n SupportedUICultures = supportedCultures\r\n });\r\n\r\n app.UseMvc(routes =>\r\n {\r\n routes.MapRoute(\r\n name: \"default\",\r\n template: \"{controller=Home}\/{action=Index}\/{id?}\");\r\n });\r\n}<\/pre>\n\n
\n<\/strong>“QueryStringRequestCultureProvider”<\/em>, “RequestCultureProvider”<\/em> i\u00e7erisinde ilk provider olarak kay\u0131tl\u0131d\u0131r. Query string \u00fczerinden localization i\u015flemini ger\u00e7ekle\u015ftirmektedir. \u00d6rne\u011fin: “http:\/\/localhost:5000\/?culture=en-US<\/em>“<\/li>\n
\n<\/strong>“CookieRequestCultureProvider”<\/em> ise kullan\u0131c\u0131n\u0131n se\u00e7mi\u015f oldu\u011fu culture’\u0131, cookie bilgisini kullanarak track edebilmeyi sa\u011flamaktad\u0131r.<\/li>\n
\n<\/strong>“AcceptLanguageHeaderRequestCultureProvider<\/em>” ise kullan\u0131c\u0131n\u0131n browser’\u0131nda \u00f6n tan\u0131ml\u0131 olarak gelen culture bilgisine g\u00f6re, uygulaman\u0131n localize edilmesini sa\u011flamaktad\u0131r.<\/li>\n<\/ol>\npublic void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n{\r\n app.UseRouter(routes =>\r\n {\r\n routes.MapMiddlewareRoute(\"{culture=tr-TR}\/{*mvcRoute}\", _app =>\r\n {\r\n var supportedCultures = new List<CultureInfo>\r\n {\r\n new CultureInfo(\"tr-TR\"),\r\n new CultureInfo(\"en-US\") \r\n };\r\n\r\n var requestLocalizationOptions = new RequestLocalizationOptions\r\n {\r\n DefaultRequestCulture = new RequestCulture(\"tr-TR\"),\r\n SupportedCultures = supportedCultures,\r\n SupportedUICultures = supportedCultures\r\n };\r\n\r\n requestLocalizationOptions.RequestCultureProviders.Insert(0, new RouteDataRequestCultureProvider());\r\n _app.UseRequestLocalization(requestLocalizationOptions);\r\n\r\n _app.UseMvc(mvcRoutes =>\r\n {\r\n mvcRoutes.MapRoute(\r\n name: \"default\",\r\n template: \"{culture=tr-TR}\/{controller=Home}\/{action=Index}\/{id?}\");\r\n });\r\n });\r\n });\r\n}<\/pre>\n2) Elasticsearch \u0130\u00e7erisinde Globalization<\/h4>\n
<\/a><\/p>\nnamespace ASPNETCoreAndESearch.Business\r\n{\r\n public interface IProductService\r\n {\r\n Task CreateIndexAsync(string indexName);\r\n Task<bool> IndexAsync(List<Product> products, string langCode);\r\n Task<ProductSearchResponse> SearchAsync(string keyword, string langCode);\r\n }\r\n}<\/pre>\nnamespace ASPNETCoreAndESearch.Business\r\n{\r\n public class ProductService : IProductService\r\n {\r\n private readonly ElasticClient _elasticClient;\r\n\r\n public ProductService(ConnectionSettings connectionSettings)\r\n {\r\n _elasticClient = new ElasticClient(connectionSettings);\r\n }\r\n\r\n public async Task CreateIndexAsync(string indexName)\r\n {\r\n var createIndexDescriptor = new CreateIndexDescriptor(indexName.ToLowerInvariant())\r\n .Mappings(m => m.Map<Product>(p => p.AutoMap()));\r\n\r\n await _elasticClient.CreateIndexAsync(createIndexDescriptor);\r\n }\r\n\r\n public async Task<bool> IndexAsync(List<Product> products, string langCode)\r\n {\r\n string indexName = $\"products_{langCode}\";\r\n\r\n IBulkResponse response = await _elasticClient.IndexManyAsync(products, indexName);\r\n\r\n return response.IsValid;\r\n }\r\n\r\n public async Task<ProductSearchResponse> SearchAsync(string keyword, string langCode)\r\n {\r\n ProductSearchResponse productSearchResponse = new ProductSearchResponse();\r\n string indexName = $\"products_{langCode}\";\r\n\r\n ISearchResponse<Product> searchResponse = await _elasticClient.SearchAsync<Product>(x => x\r\n .Index(indexName)\r\n .Query(q =>\r\n q.MultiMatch(mp => mp\r\n .Query(keyword)\r\n .Fields(f => f.Fields(f1 => f1.Name, f2 => f2.Description)))\r\n ));\r\n\r\n if (searchResponse.IsValid && searchResponse.Documents != null)\r\n {\r\n productSearchResponse.Total = (int)searchResponse.Total;\r\n productSearchResponse.Products = searchResponse.Documents;\r\n }\r\n\r\n return productSearchResponse;\r\n }\r\n }\r\n}<\/pre>\nnamespace ASPNETCoreAndESearch.Controllers\r\n{\r\n public class HomeController : Controller\r\n {\r\n private readonly IProductService _productService;\r\n\r\n public HomeController(IProductService productService)\r\n {\r\n _productService = productService;\r\n }\r\n \r\n public async Task<IActionResult> Index()\r\n { \r\n string indexName = $\"products\";\r\n await FeedProductsInTurkish(indexName, \"tr\");\r\n await FeedProductsInEnglish(indexName, \"en\");\r\n\r\n return View();\r\n }\r\n\r\n public async Task<IActionResult> Products(string keyword)\r\n {\r\n var requestCultureFeature = Request.HttpContext.Features.Get<IRequestCultureFeature>();\r\n CultureInfo culture = requestCultureFeature.RequestCulture.Culture;\r\n \r\n ProductSearchResponse productSearchResponse = await _productService.SearchAsync(keyword, culture.TwoLetterISOLanguageName);\r\n\r\n return View(productSearchResponse);\r\n }\r\n\r\n private async Task FeedProductsInTurkish(string indexName, string lang)\r\n {\r\n List<Product> products = new List<Product>\r\n {\r\n new Product\r\n {\r\n ProductId = 1,\r\n Name = \"Iphone X Cep Telefonu\",\r\n Description = \"G\u00fcm\u00fc\u015f renk, 128 GB\",\r\n Price = 6000\r\n },\r\n new Product\r\n {\r\n ProductId = 2,\r\n Name = \"Iphone X Cep Telefonu\",\r\n Description = \"Uzay grisi rengi, 128 GB\",\r\n Price = 6000\r\n },\r\n new Product\r\n {\r\n ProductId = 3,\r\n Name = \"Rayban Erkek G\u00f6zl\u00fck\",\r\n Description = \"Ye\u015fil renk\"\r\n },\r\n new Product\r\n {\r\n ProductId = 4,\r\n Name = \"Rayban Kad\u0131n G\u00f6zl\u00fck\",\r\n Description = \"Gri renk\"\r\n }\r\n };\r\n\r\n await _productService.CreateIndexAsync($\"{indexName}_{lang}\");\r\n await _productService.IndexAsync(products, lang);\r\n }\r\n\r\n private async Task FeedProductsInEnglish(string indexName, string lang)\r\n {\r\n List<Product> products = new List<Product>\r\n {\r\n new Product\r\n {\r\n ProductId = 1,\r\n Name = \"Iphone X Mobile Phone\",\r\n Description = \"Silver color, 128 GB\",\r\n Price = 6000\r\n },\r\n new Product\r\n {\r\n ProductId = 2,\r\n Name = \"Iphone X Mobile Phone\",\r\n Description = \"Space gray color, 128 GB\",\r\n Price = 6000\r\n },\r\n new Product\r\n {\r\n ProductId = 3,\r\n Name = \"Rayban Men's Glasses\",\r\n Description = \"Green color\"\r\n },\r\n new Product\r\n {\r\n ProductId = 4,\r\n Name = \"Rayban Women's Glasses\",\r\n Description = \"Gray color\"\r\n }\r\n };\r\n\r\n await _productService.CreateIndexAsync($\"{indexName}_{lang}\");\r\n await _productService.IndexAsync(products, lang);\r\n }\r\n }\r\n}<\/pre>\n@model ProductSearchResponse\r\n@using Microsoft.AspNetCore.Mvc.Localization\r\n@inject IViewLocalizer Localizer\r\n\r\n<div class=\"container\">\r\n <h3>@Localizer[\"Toplam {0} \u00fcr\u00fcn bulundu.\", Model.Total]<\/h3>\r\n <table class=\"table\">\r\n <thead>\r\n <tr>\r\n <th>Id<\/th>\r\n <th>@Localizer[\"\u0130sim\"]<\/th>\r\n <th>@Localizer[\"A\u00e7\u0131klama\"]<\/th>\r\n <th>@Localizer[\"Fiyat\"]<\/th>\r\n <th><\/th>\r\n <\/tr>\r\n <\/thead>\r\n <tbody>\r\n @foreach(var product in Model.Products)\r\n {\r\n <tr>\r\n <td>@product.ProductId<\/td>\r\n <td>@product.Name<\/td>\r\n <td>@product.Description<\/td>\r\n <td>@product.Price<\/td>\r\n <\/tr>\r\n }\r\n <\/tbody>\r\n <\/table>\r\n<\/div><\/pre>\ndocker run -p 9200:9200 -p 9300:9300 -e \"discovery.type=single-node\" docker.elastic.co\/elasticsearch\/elasticsearch:6.0.1<\/pre>\n
public void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddMvc();\r\n\r\n services.AddSingleton(x => new ConnectionSettings(new Uri(\"http:\/\/localhost:9200\")));\r\n services.AddTransient<IProductService, ProductService>();\r\n}<\/pre>\n<\/a><\/p>\n