
Dead simple auditing for ASP.NET Core apps
I wanted a reusable way of auditing database changes that required minimal setup, but would allow me to see what happened to an entity when it was changed.
I finally got around to creating one.
My rambling thoughts on exploring the .NET framework and related technologies

I wanted a reusable way of auditing database changes that required minimal setup, but would allow me to see what happened to an entity when it was changed.
I finally got around to creating one.

How I ditched WordPress and used Copilot to write a no-WordPress, no-database, no-PHP fast and simple blogging platform

I have mentioned before that Copilot doesn't have a very high opinion of my coding skills. I'm not offended by this, it just adds to my opinion of Copilot's inline suggestions (which I find to be generally of a very poor quality, usually with compiler errors).
I have mostly got used to this, and just hit Esc when it suggests these sorts of things. However, it was really insistent just now.

I have a Blazor app that I've been developing for a while, and wanted to add a migration. Done this plenty of times before, so didn't expect anything unusual.
Instead of the usual success, I saw the following exception... The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: System.Management.Automation.RemoteException.
No, I didn't know what that meant either! Now I do, and if you read my ramblings, you will as well.

I've been working on a mixed-mode Blazor app for some time, and noticed that every now and then, when it switched from server rendering to WASM, I would see the page content briefly, then the browser tab went black, and I got a crash message. It took some hours of hard work, which ended up being an Edge bug, nothing to do with my code.