Developing multicultural web applications is a challenge for many developers, even experienced ones. This article provides step-by-step tutorial for building a multicultural web application starting from the standard project template for ASP.NET Core 2.1 razor pages, and it addresses most known localization problems and provides solutions for them.

Creating a dropdown navigation menu according to supported cultures list, dropdown language menu will help us switch between cultures easily

Localize request via according to provided route value

In a public website, route value is the best option for localization because people must be able to share page links for any selected culture. There is more options like query string parameter, cookies and accepted page header value, but we will focus on route value.

Creating standard ASP.NET Core 2.1 web application project without authentication for startup

Some cultures uses calendars other than Gregorian like Hijri and Hebrew, here we will see how to force Gregorian calendar for other cultures as well.

Override Required validation attribute error message with custom error message.

A short comparison between resource files for localization usage in razor pages.