EF Core, C# 14 and performance fixes
Practical .NET reads on EF Core LINQ, C# 14 null-safe assignment, performance tips, route constraints, caching, and Visual Studio workflow.
Jasen's top three picks
- 1 When Static Validations No Longer Have Power
medium.com
A reconfigurable validation approach that uses compiled expressions when static rules stop being enough.
- 2 EF Core + LINQ: The Real-World Guide Every C# Developer Wishes They Had Earlier
towardsdev.com
A practical EF Core and LINQ guide that focuses on real-world query behavior instead of textbook examples.
- 3 ToList() vs ToArray() in C#: The Performance Guide Every Developer Needs
towardsdev.com
A memory-minded comparison of ToList() and ToArray() that makes the tradeoffs easy to apply.
Editor's note
I pulled a deliberately mixed lineup this time: EF Core LINQ behavior, C# 14 null handling, performance tuning, and a few workflow pieces. The cache deep dive and the route-constraints guide stood out for being immediately useful in real projects, not just academically interesting.
Today's articles
When Static Validations No Longer Have Power
medium.com
Reconfigurable Request Validations Using Compiled Expressions in .NET
Topics: C#
Read articleEF Core + LINQ: The Real-World Guide Every C# Developer Wishes They Had Earlier
towardsdev.com
A practical, example-rich guide to understanding how LINQ behaves inside EF Core — with real problems, real fixes, and clean explana Continue reading on Towards Dev »
Read articleToList() vs ToArray() in C#: The Performance Guide Every Developer Needs
towardsdev.com
Most .NET developers default to ToList() without knowing it wastes 24–31% more memory. Here’s when to use ToArray() instead. Continue reading on Towards Dev »
Topics: C# Performance
Read articleDTOs in .NET
medium.com
There are two kinds of .NET APIs in the wild:
Topics: ASP.NET Core Web API
Read articleUnderstanding .NET Application Lifecycles: From Startup to Shutdown
medium.com
The lifecycle of a .NET application encompasses the entire journey from the moment your code begins execution until the application…
Topics: .NET Core
Read articleBuild, Rebuild, and Clean Solution — Explained Like You Actually Need It
medium.com
If you’ve ever paused over Build Solution, Rebuild Solution, or Clean Solution in Visual Studio, wondering “Which one should I click now?”…
Topics: Visual Studio
Read articleASP.NET Core route constraints: A quick guide for developers
roundthecode.com
Learn ASP.NET Core route constraints in this quick guide for developers. Fix routing issues fast and improve API accuracy with simple, clear examples. The page ASP.NET Core route constraints: A quick ...
Topics: ASP.NET Core Web API
Read articleWhy Choose C# and .NET as My Programming Language?
news.google.com
Why Choose C# and .NET as My Programming Language?
Read articleBuilding Your Own Mediator Pattern in Modern .NET
medium.com
I demonstrate how to build a custom implementation of the mediator pattern. Complete with a pipeline, notifications, and performance.
Topics: Design Patterns MediatR Performance
Read articleC# 14 Null-conditional Assignment: Complete Guide to Elegant Null Handling
laurentkempe.com
If you've been working with C# since the introduction of null-conditional operators in C# 6.0, you've likely appreciated how ?. and ?[] simplified null-checking when reading values. But what about wri...
Read articleHow to Build a High-Performance Cache Without External Libraries
milanjovanovic.tech
Learn how to build a high-performance cache from scratch in .NET, moving from a simple ConcurrentDictionary to an optimized keyed-locking system. This deep dive explores how to master concurrency patt...
Topics: C# Performance Redis
Read articleC# 14’s Null-Safe Member Assignment — Stop Writing Null Checks
codeexact.medium.com
Say goodbye to verbose null-checking boilerplate. C# 14 introduces null-safe member assignment — a practical feature that lets you check…
Topics: C#
Read articleStop using Exceptions to control flow in .NET. It’s time to embrace the “Result” pattern.
medium.com
Why try/catch blocks are ruining your API's readability and performance, and the functional approach senior developers use instead.
Topics: C# Solid Principles
Read article