You already have a
ASP.Net project with Localization all set up and localized. Sure, you could convert the
resx files and use Internationalization (i18n) built into Angular 2+. Well, another option is to keep the whole setup the same, and still let the server-side handle everything. This small tutorial won’t go over date and time, only string localization. Keep in mind you will not be loading all languages, rather only the one the browser is set to. So if for reasons you wanted to load all languages, for example, no refresh language change, this approach will need some modifications.
The prereqs are that you already have a project set up with your localization file already being used. An example is on any cshtml page, you should simply be able to localize using
LocalizationProjectName.The_Key. Moving on, you also have an angular 2+ project already set up. If you don’t, you could use a seed project to test this out.