LocalizationProvider Client Side Feature now also for Asp.Net Mvc Apps

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…

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

Object Cache Viewer Joins EPiServer Developer Tools

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…

Keep reading

How Risky are EPiServer.DeveloperTools on Production Environment?

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…

Keep reading

Capture Exception in Azure Functions Poison Queue Trigger

I'll not talk about how cool Azure Functions are (because they are cool), but will focus on pretty tiny but very important aspect when running functions - how to get exception details out of poison message when using [QueueTrigger] trigger on Azure Storage Queues and "normal" handling of the message just fails and runtime decides to move message to poison queue. Code samples are provided for Azure Functions V2, but guess it applies to previous version as well. Queue Message Handler To have a queue message handler in…

Keep reading