A developer found an IDOR flaw in their own security test, where an endpoint returned records without checking that they belonged to the caller. The article explains why [Authorize] alone cannot cover ownership and how to make the check hard to forget.
The new FullJoin method in .NET 11 returns matched pairs plus unmatched rows from both sides as (Outer, Inner) tuples. Join, LeftJoin, RightJoin and GroupJoin also gain overloads without a result selector. The feature is in .NET 11 RC2, so details may still change before the final release.
Part 5 of the Transmitly eShop series shows how delivery updates that arrive after dispatch are captured and stored. Provider webhooks, such as Twilio status callbacks, are normalized into one DeliveryReport model and saved in a Communications database. It is a practical reference for building message history and delivery tracking in ASP.NET Core.
.NET 11 RC2 adds Process.RunAndCaptureText, which runs an external command, drains stdout and stderr together and returns both strings with the exit code. It removes the deadlock that the classic redirect-and-ReadToEnd pattern can hit on noisy tools. Anyone who shells out to git, ffmpeg or internal CLIs will want to know the new helpers and their timeout behavior.
A practical guide to Unity native plugins on Android and iOS, arguing that the hard part is not the native calls but threading, build configuration and release stripping. It covers a single C# interface with an editor fake, marshalling callbacks to the main thread, and CI checks for both platforms.
C# 14, shipped with .NET 10, adds extension members: extension properties, static members and operators declared inside extension blocks. This goes beyond the classic this-parameter extension methods and lets APIs read more naturally. Knowing the current limits, such as no state and no indexers, matters before adopting it in production.
This article walks through how the .NET 10 runtime's ReadOnlySpan<char>.IndexOf finds a substring using SIMD vector instructions. The author compares it with a naive loop in a BenchmarkDotNet run and explains where the speed difference comes from. It is a useful deep dive for developers who care about string search performance.