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.…

It's super cool to work together with the community and unite effort across all areas to strengthen EPiServer ecosystem and toolsets. After chat with Joe Mayberry we decided that his local object cache viewer would be great addition to EPiServer DeveloperTools. Thanks to Joe's contributions local object cache viewer is now part of EPiServer DeveloperTools package. During the merge we added small extra to the tool - you can now also see approx. size of the cache entry (might be sometimes useful to know who ate the cake). Code to…

We had a great conversation at the EPiServer Partner Close-Up conference with one and only Allan Thræn about future plans and such. And one of the topics we chatted about was that in our opinion no one really knows whether "EPiServer.DeveloperTools" package is safe to install to production environment or not. Will it do any harm? It's great for local development and probably staging also. But what about production? What exactly the package does, what it intercepts, mimics or changes in the running code?! Therefore I thought…