Background During development of DbLocalizationProvider I had single repository in GitHub containing more that one package as result of the build. Initially there was just a EPiServer package to add support for database driven localization resources. Later realized that there is actually not so much to do to add support for Asp.Net Mvc (.NET Framework) applications and later also for .NET Core applications. This results into: packages for EPiServer applications packages for Asp.Net Mvc applications packages for Asp.Net Core applications abstract/core packages containing only general purpose…

There are sometimes moments when you just need to take deep inhale and add backward support for apps that most probably you will hardly see selected in "File > New Project". We do have some projects still based on "pure" Asp.Net Mvc that need client-side localization. Therefore adding support for this type of apps sounds like feature with "must have" label. At least for now. This applies to v5.5.1 and forward. However, if you are targeting .NET Core - support is…

Starting with v5.4.1 version of the LocalizationProvider package for .NET Core, it's now possible to work with translations also on client-side.…

Time to time I receive questions on how to properly translate System.Enum based properties on Episerver using DbLocalizationProvider package. The support has been around for quite while, but I've never really blogged about it properly.…

This blog post is describing configuration setup required to support dynamically generated area names for Razor Class Library Pages. This approach is used in AdminUI for DbLocalizationProvider for Asp.Net Core.…