Localization has been around since .NET 1.1. Looking at the interfaces of ResourceManager and CultureInfo, along with the static nature of resource access, its easy to see the ties to legacy client technology WinForms. With the release of ASP.NET Core, developers have new tools to work with localization in the realm of server-based web apps.

We’ll explore these new mechanisms and how the ASP.NET team designed them to work in a web-centric world. You’ll need a new Razor Pages project to follow along, or you can clone the complete solution from the GitHub repository: https://github.com/khalidabuhakmeh/aspnetcore_localization_sample

## More Resources

Some of the resources utilized to write this tutorial are listed below:

Rider and ReSharper – https://www.jetbrains.com/dotnet/
Mike Brind – https://www.mikesdotnetting.com/article/346/using-resource-files-in-razor-pages-localisation
.NET Core tutorials – https://dotnetcoretutorials.com/2017/06/22/request-culture-asp-net-core/
Microsoft Documentation – https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization?view=aspnetcore-3.1
Alan Edwardes – https://alanedwardes.com/blog/posts/country-code-to-flag-emoji-csharp/)