.NET 8 and .NET 9 both leave support on November 10, 2026, and the in-process model for Azure Functions ends the same day. The author argues that the target framework is rarely a one-line change, because version pins hide in Directory.Build.props, global.json, Dockerfiles, CI workflows and Functions setup.
EF Core 10 with Npgsql 10 maps a .NET complex type to a PostgreSQL jsonb column using ToJson(). The article shows how LINQ property access becomes ->> SQL, which index types serve which queries, and when a jsonb column beats a separate EAV table. It is a practical guide for models with many sparse optional fields.
EF Core 11 lets the dotnet ef command-line tool read default options from a .config/dotnet-ef.json file. When your DbContext lives outside the startup project, you no longer need to repeat --project and --startup-project on every migration or database command. The tool finds the nearest config by walking up the folder tree, and explicit command-line flags still take precedence.
How should a warehouse order API refuse illegal state changes, short stock, stale ETag writes and malformed JSON? The author builds a pick-pack-ship demo on .NET 10 Minimal APIs and EF Core 10, mapping each refusal to a specific status code, such as 409, 412 and 400. He also explains why an exact retry should return 200 instead of an error. A useful guide for anyone designing workflow endpoints.
Part 3 of Scott Galloway's series builds a temporal predictor in C#. It tracks a journey's centroid, velocity and acceleration in real time, then forecasts whether it ends in purchase, cancellation or departure within 60 seconds. The engine learns only from actual endpoints and abstains when evidence is thin, which makes it a concrete example for teams building SQLite-backed behavioural or service-health models.
Mauro Servienti uses a shipping notification that arrived seven times to explain how duplicate messages happen in messaging systems. The post separates duplicates caused by sending, receiving and processing, and lists practical defenses for each. It is a useful read for any .NET developer building queue-based systems.