This category mostly contains hacks and workarounds that are definitely not needed, recommended, or even safe in production environments. So, beware – don’t apply or run these against your production at all. These should be limited to the development environment only.
Okay – another one of the topics that I’m explaining probably more to myself than whoever’s reading this later. But that’s why I write this blog, so please bear with me. 🙂 Anyway, onto the actual issue at hand! I was configuring Docker on WSL on my Windows laptop for development purposes. That’s supposed to be easy – install WSL, install a distribution, install Docker, switch it to using WSL,…Continue reading Upgrade from WSL 1 to WSL 2 in Windows 10 to fix Docker
Another one in the series of “random things that break when you try to run Docker on Windows”! I was just minding my own business, trying to run an Azure IoT Edge custom module – a Docker container, really – locally, when suddenly everything broke and one of my Docker containers wouldn’t run anymore, which broke the rest of my stuff pretty badly. Instead, it failed with a cryptic and…Continue reading How to fix “exec user process caused: no such file or directory” in Docker on Windows?
This was another (luckily pretty shallow) rabbit hole down some corporate IT and weird default configurations by our favorite tech-daddy Microsoft. In this article, I will describe one possible reason for a process called Vmmem.exe consuming enough RAM to crash pretty much everything else running on your machine. But let’s take a step back first – what happened? Problem I was developing some Azure IoT Edge modules (as one does),…Continue reading How to solve Vmmem consuming ungodly amounts of RAM when running Docker on WSL?
Another fun one with Azure Functions! At least it’s a simple one: this time, I ran into a weird issue while doing some code reusing – well, copy-pasting – between a couple of different projects. I was lovingly hand-crafting some Azure Functions, while suddenly the Azure Functions host would throw this in ugly red letters: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: ‘Microsoft.AspNetCore.Mvc.Core, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60’ at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters) at…Continue reading Azure Function build fails with “Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: Microsoft.AspNetCore.Mvc.Core”
Ah – this was a fun one. I needed to figure out how to purge, flush and clear your commit history on GitHub. Turns out it isn’t as easy as clicking a button in the web user interface – the world is apparently not ready yet! 😁 Luckily, it wasn’t that complicated either – and the steps should work for other flavors of git as well. Background Always remember to…Continue reading How to nuke your Git(Hub) commit history?
This article explains another fun issue that you might run into when developing Azure Functions in your local environment. It was weird how unclear the few results were that I could find. 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…Continue reading ILogger binding suddenly failing for Azure Functions – what to do?
This article describes how to fix and tweak your pre-build directives in Visual Studio – just in case they refuse to work properly. Because yeah, apparently that sometimes just randomly happens. But fear not – there’s a stupid and ugly, but definitely thoughtful workaround available! Also, sorry for the confusing title. I’m taking suggestions for a more descriptive one – but this one was kind of difficult to word clearly.…Continue reading How to fix a build configuration that’s not available as a build directive in Visual Studio?
Building a proof-of-concept on .NET Core 3.0 preview 7 I ran into issues when developing web APIs. This release is production-ready (according to Microsoft -see below), but every now and then you run into really unintuitive and sometimes surprising issues. Go LiveNET Core 3.0 Preview 7 is supported by Microsoft and can be used in production. We strongly recommend that you test your app running on Preview 7 before deploying…Continue reading How to resolve build failing with .NET Core 3 and Microsoft.AspNetCore.Mvc.Versioning
Instead of being stuck on whatever version your SPFx project was originally created with, it’s possible and sometimes required to upgrade it afterward to gain access to newer functionalities like integration with Microsoft Teams. This process, to me, is comparable to updating the .NET Framework version in your classic web application projects – while it’s sometimes a matter of simple configuration change and a rebuild, most of the time there…Continue reading How to update SharePoint Framework for an SPFx webpart?