Editor's note
I pulled together a deliberately mixed lineup this time, from scoped services in background workers to Redis caching and RabbitMQ-based workers. I also liked the practical takes on value objects and thin controllers, since both touch everyday design tradeoffs most teams feel.
ASP.NET Core, design, and ops picks
If Tuesday were a car, it would be the trusty sedan—not as flashy as Monday's sports car wake-up call or laid-back like Friday's convertible vibe, but it's got depth and mileage, ready to navigate the zigs and zags of .NET development. As we cruise through today's articles, let’s draw on our seasoned instincts, spotlighting insights that’ll fine-tune your coding engine. Slide into this reflective journey and expect the unexpected as we delve into the nuances that only a Tuesday can serve—a day perfect for tuning up skills and charting steady progress.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
How do you resolve scoped services in a background service?
A good refresher on why background services need a scope factory, not a direct scoped dependency.
CRUD Operations in ASP.NET Core with Entity Framework – Real-World Example
A practical CRUD walkthrough that stays close to how many teams actually build ASP.NET Core apps with EF Core.
String, StringBuilder, Span: The Secrets to Better Code
A useful comparison of string, StringBuilder, and Span for people who still care about allocations.
Covers automated testing basics without overcomplicating the conversation.
Temp Tables vs CTEs in SQL Server: What You Should Really Know
A solid reminder that SQL Server temp tables and CTEs solve different problems, even if they look interchangeable at first.
Highlights new CMake Tools improvements in VS Code, even though it sits a bit outside the usual .NET lane.
.SLN is dead. Long live .SLNX!
A short take on SLN versus SLNX that should interest anyone watching the solution file format evolve.
Vibe coding: a blessing or a curse for .NET developer?
A timely opinion piece on vibe coding and where it helps or hurts .NET developers.
Walks through operational concerns in .NET Core, which is where many projects get real-world scars.
How to Use Value Objects to Solve Primitive Obsession
Value objects are presented as a concrete way to push back on primitive obsession.
Scalable Logging Pipelines in .NET: Serilog, Seq, and Elastic Stack Explained
Serilog, Seq, and Elastic get a practical treatment for scaling logs without turning observability into noise.
The Death of var (In My Codebase)
The case against banning var outright is worth reading, because readability rules are rarely absolute.
Rust or C#? : Developer Security Quick Fire Questions @ MS Build
A quick security-flavored MS Build clip that’s more fun than formal.
10 Underrated C# Features You Should Be Using
A good list of underrated C# features that can still improve day-to-day code.
Why You Should Start Using Visual Studio Code for Your .NET Projects
Makes the case for VS Code in .NET work, especially for teams that want a lighter editor.
Understand GitHub Copilot Extensions and Slash Commands
Copilot extensions and slash commands are explained clearly enough to help you decide if they fit your workflow.
Scaling ASP.NET Core Apps with Redis Output Caching
Redis output caching is shown as a straightforward scaling lever for ASP.NET Core apps.
Repository Pattern & Clean Architecture With Entity Framework Core in .NET 9
Repository pattern plus clean architecture in .NET 9 will appeal to teams still shaping their boundaries.
The Dark Side of Thin Controllers in .NET: Fat Services and Hidden Technical Debt
Thin controllers can hide fat services, and this piece calls out the technical debt tradeoff well.
Building Distributed .NET Background Workers with RabbitMQ and MassTransit
RabbitMQ and MassTransit make for a solid distributed worker combo, especially when background jobs stop being simple.
Self-Healing .NET Apps: Building Systems That Recover Themselves
Self-healing apps is an ambitious topic, but the article is a useful entry point into recovery-oriented design.



















