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.
These posts are arguably closely related to my other category, software development (or DevTips).
This article offers a stupid workaround for a cryptic and seemingly unrecoverable problem that manifests itself after a Visual Studio / .NET update and causes the following error to be thrown: “There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier ‘browser-wasm’.” Sorry, no real solution here –…Continue reading How to fix “There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier…” after a Visual Studio update?
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…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…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…Continue reading How to solve Vmmem consuming ungodly amounts of RAM when running 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…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…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,…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…Continue reading How to fix a build configuration that’s not available as a build directive in Visual Studio?
This article describes a solution to an error “Insufficient memory to continue the execution of the program.” I was debugging an Azure Function locally and ran into it – it stopped my Azure Function from starting at all. So, this is what I got: Insufficient memory to continue the execution…Continue reading How to resolve error “Insufficient memory to continue the execution of the program.” when debugging Azure Functions locally?
Whilst 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…Continue reading How to resolve build failing with .NET Core 3 and Microsoft.AspNetCore.Mvc.Versioning
