Asp.Net Core localization, powered by online translation, auto resource creating and more...

Image for post
Image for post


Developing a multi cultural web application requires building the localization infrastructure that will process the request localization and localize views, error messages, …etc. On the other hand; every localized culture requires at least one resource file, filled with all localized key-value pairs.

Building the localization infrastructure and filling the resource files can take a lot of time and effort. XLocalizer has been developed from scratch to solve these two issues and free the developer from unnesseary workload.

What does XLocalizer offers?

Simple localization setup: First of all, it is built to help developers create localized web applications easily without wasting time on developing localization infrastructure. …

UPDATE — 14.Nov.2020: This tutorial is based on “LazZiya.ExpressLocalization” nuget that was developed in early 2019. Recently, I’ve developed a new localization nuget named “XLocalizer”, it is easier to configure and has more powerful capabilities like localization powered by online translation, auto resource creating and more. Click here to go to the new XLocalizer tutorial, or keep reading below for the older nuget.


Localization/globalization in ASP.NET Core requires a lot of infrastructure setup and it consumes time and effort. In this article, I’ll show how to easily localize Asp.Net Core web applications using a nuget package called LazZiya.ExpressLocalization.


Most of the web apps use URL based localization, so we can see the selected culture in the URL, e.g., ASP.NET Core provides below request culture providers by…


Ziya Mollamahmut

Software Developer, Regional Training Expert, 3D Modeling Hobbyist

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store