Static sites can easily be hosted for free by (e.g) GitHub Pages or Azure Storage, but if you have a contact page you'll need something to send the emails. Here's a configurable .NET Core 3 Azure Function which does that.
The ReadableExpressions Expression debugger visualizers now show colourized, themeable source code, with a variety of translation options.
Moq provides various ways of setting up and verifying behaviour, and I've recently seen some confusion over how. So here's some examples and pointers.
Legacy systems are commonplace, but it's difficult to come up with anything concrete to justify the expense of an update to someone with an eye on the bottom line. Thankfully, the folks at NDepend have now built technical debt computation on top of their code analysis tools, giving you a much easier way to have these sorts of discussions. Here's a real-world example.
I'm currently updating a legacy ASP.NET WebForms application to ASP.NET Core. Because big rewrites (almost) never work, it's a case of migrating sections of the site one at a time, having WebForms pass specific requests to ASP.NET Core, with no change to the end user's experience. Here's how.