Episerver ContentArea with AllowedTypes Specified by Interface

Background Once an interesting question was asked on Episerver Community Slack space how to work with ContentAreas and specifically [AllowedTypes] and specify restrictions based on interface. My answer wasn't quite helpful there and also I'm quite passionate about looking into the foreign code and understanding how platform is built - so I decided to write up a bit expanded version of the answer. According to aforementioned question you might have for example page type with following ContentArea definition (based on AlloyTech sample site): [ContentType(GUID = "19671657-B684-4D95-A61F-8DD4FE60D559")] public class…

Keep reading

Episerver DeveloperTools - UI Refresh

This blog post is about latest features and bug fixes added to v3.5 of Episerver DeveloperTools package…

Keep reading

Building Real-time Public Transport Tracking System on Azure - Part 1

This is 1st post in series about real-time public transport tracking system development based on Azure infrastructure and services. Blog posts in this series: Part 1 - Scene Background & Solution Architecture Part 2 - Data Collectors & Composer Part 3 - Event-Based Data Delivery Part 4 - Data Distribution with SignalR & gRPC Servers We are working with transportation company where real-time systems is everyday mindset for each team member. Over few years we have been part of building this system. There were few generations (differences between systems were…

Keep reading

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