#.net core localizer view how to

For my example they are added under the Resources folder. How can set this up?įirst we need to add in the resx files which include the different locale versions of the data which we want to use. This leaves the http header Accept-Language and the AcceptLanguageHeaderRequestCultureProvider. Apis should not be reliant on cookies, as it's a web technology, they could be called from web applications, mobile devices or desktop applications not all which understand or should deal with cookies. The cookie option is a big no no when it comes to api design.

AcceptLanguageHeaderRequestCultureProviderįor Api developers using the querystring does not allow for the the business requirement of the data, it would also just get in the way.

The Request Culture Providers look at various different settings and then set the Culture and UICulture values. There are a number of Request Culture Providers which are loaded into the pipeline automatically. Can Accept-Language Header be used in an api?

The other option is using the Accept-Language http header which is usually set by your browser from your operating systems preferences. This is sometimes done through a language dropdown on a website where you can pick your language. You want to make your application open to a wider audience and to do that one of the items you can work with is language. Localisation is the way in which you alter your website, application or api to be available and open for multiple areas of the world. It was an interesting idea and I remember there wasn't a good localisation story in earlier version of ASP.NET Core however with the previews of 2.2 coming out I thought I would investigate and see if I could use it from an api perspective. I was sure it was possible, but then they said that it wasn't a web front end but the values and error messages from a web api I was intregued.

#.net core localizer view how to

You can also make it last, or just make the list of providers whatever you want.Īndrew Lock has a great article on setting up this option as an MVC filter as well.I was asked at work the other day if I knew how to get localised error messages in ASP.NET Core. Note that we also insert the provider at index 0, so it will be checked first always. The defined route uses a catch-all parameter Here we use a router to grab the culture from the URL and set up the route data before Then we need to add the request localization middleware to Configure in Startup: public void Configure(IApplicationBuilder app, IHostingEnvironment env)Īpp.UseRequestLocalization(new RequestLocalizationOptionsĭefaultRequestCulture = new RequestCulture('en-US'), If you do not specify a resources path, the resource files will be expected to It also specifies that we will use a folder called Resources to put our This adds the necessary services for localization to the service container. We will put our translations in a folder called Resources To this: public void ConfigureServices(IServiceCollection services) Configuring Startupįirst, we will simply change the ConfigureServices method in the Startup class The easiest way is to use VS 2017 and create a new ASP.NET Core MVC project.

Will already have these in all projects by default. These are all part of the meta-package so most 2.0 developers view localization, data annotation localization (Included in ) : MVC Core Localization components, e.g.You may need others for different things as well: Let's start with something really simple.įirst off, you'll need the NuGet package. If you have a problem with 1.X, leave a comment, and I'll make sure This has been written from the point of view of ASP.NET Core 2.0. It's quite long, but I tried to focus the important stuff here This article covers pretty much all the important things about localization in