This article explains how to fix an annoying issue with Microsoft’s SDK for CosmosDb v3 – it comes with a Newtonsoft.Json dependency, that most of Microsoft’s recent packages have let go of. With .NET Core 3.1 having shipped with System.Text.Json included, and (mostly) replacing Newtonsoft.Json, it’s kind of the preferred option. However, CosmosDb v3 SDK doesn’t support it and by default requires you to use Newtonsoft.Json to override the property names, if you want to – for example – map entities with PascalCase naming with…Continue reading System.Text.Json.JsonPropertyName not working for CosmosDb in .NET Core/5?
Man, do I run into all kinds of issues with the smallest Azure Functions that I develop. And it’s mostly my fault. The silver lining is that you’re here to read this article, so you probably ran into this same stuff. Well – you should be happy to hear this article describes fixes to a couple of issues – let’s see if they help you out as well! The article probably largely applies to any situation where you have a project referencing another project and…Continue reading Errors loading an assembly that’s using Microsoft Graph API
This article explains another fun issue you might run into, when developing Azure Functions in your local environment. It was weird how unclear the few results I could find were, and the issue is just… Very hazy in general. But I was able to track the issue down, and thought I’d document the solution :) It’s for myself, really, because I’m pretty sure I’ll run into this one again. But if you find it useful, good for you! 😉 Problem So what is it, that’s…Continue reading ILogger binding suddely failing for Azure Functions – what to do?