.Net Core

Converting Azure WebJobs to .NET Core

Motivation Migrating something to .NET Core (while stuck with .NET Framework for a while due to surrounding platform dependency constraints) sounds intriguing and challenging at the same time. Our main motivator for the migration has been performance improvements, performance improvements and upcoming performance improvements seen throughout .NET Core. This blog post will walk you through steps we did for migration for one our web jobs over to .NET Core. As seen from pull request statistics - it's actually more removal that adding new code. Throwaway always feels good. Path wasn't…

Keep reading

LocalizationProvider v5.7 Is Out

It's been a while since last Episerver DbLocalizationProvider package update. Fortunately this release includes couple bug fixes delivered by amazing developer community and also few new features. What's included in this release: "Transient" referenced projects are now properly respected and scanned (#github/28) Resource import in Episerver was not polite and threw up when importing not active/disabled languages (#github/30) Duplicate keys are ignored and first one is taken during MigrationTool process (#pull/25) There are also some other smaller bug fixes, but who really reads release…

Keep reading

Client-side Localization in Asp.Net Core Using LocalizationProvider

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

Keep reading

Localization Provider - 5th generation out!

Freshly baked v5.0 is out now. Changes in this version (some of them are breaking ones). Mostly release was focused on .Net Core AdminUI improvements and new features.…

Keep reading

Fixing ClientModel Validation in Asp.Net Core

This blog post is about how to fix Asp.Net Core Mvc built-in client model localization provider and use DbLocalizationProvider on client side as well.…

Keep reading