Article overview

.NET Job Scheduling — Hangfire and Persistent Reliability

Published on 11/27/25 5:00 pm by Martin Stühmer

Hangfire combines persistent job storage, automatic retries, and real-time monitoring to simplify background processing. Learn when database-backed reliability matters and how Hangfire scales from single instances to distributed workers.

.NET Job Scheduling — The Landscape

Published on 11/25/25 5:00 pm by Martin Stühmer

Explore the spectrum of .NET job scheduling from lightweight in-memory solutions to enterprise-grade distributed systems. Understand which approach fits your operational model and why background processing architecture matters.

NetEvolve.HealthChecks 5.0: 27+ Targeted Probes, Zero Boilerplate

Published on 11/20/25 11:00 pm by Martin Stühmer

NetEvolve.HealthChecks 5.0 is a decisive expansion—broader coverage scope, less boilerplate.

New domain‑specific packages extend monitoring across cloud services, messaging platforms, graph, time‑series, vector and AI backends. In parallel, the former inheritance‑driven shared base library (abstract classes + repetitive DI wiring) was replaced by purpose-built source generators—removing manual registration churn and consolidating intent. Release 5.0 also formalizes full support for .NET 10—aligning with current trimming and analyzer improvements.

.NET 10 Testing: Microsoft Finally Fixed the Test Runner (Mostly)

Published on 11/20/25 5:00 pm by Martin Stühmer

.NET 10 replaces VSTest with Microsoft.Testing.Platform, bringing SDK-integrated testing with faster discovery, consistent behavior across environments, and explicit configuration contracts. But it requires .NET 10, breaks old test adapters, and demands CI pipeline discipline. Here’s what actually changes, who should migrate now, and who should wait.

Code Metrics and Configuration: Beyond the Numbers Game

Published on 11/18/25 5:00 pm by Martin Stühmer

Code metrics have become a standard feature in modern development environments, yet their implementation and interpretation often leave much to be desired. While Visual Studio and .NET provide comprehensive code metrics analysis, the way these metrics are configured, presented, and (more critically) acted upon reveals a fundamental disconnect between measurement and meaningful improvement.

What code metrics actually measure, how to configure them properly, and (more importantly) why blindly following thresholds without understanding context is, frankly, a recipe for misguided refactoring efforts that waste your team’s time and actively damage your codebase.