Marten 9.52.0, the PostgreSQL-based document and event store for .NET, adds a new schema table, an exception transform option and several tenant removal fixes. Anyone upgrading should know how the schema migration affects their databases before deploying.
This guide covers how ASP.NET Core background services can stop cleanly during shutdown without losing or duplicating work. It walks through cancellation tokens, scoped dependencies, queue acknowledgement order and host shutdown timeouts, with a test checklist for production readiness.
PostSharp 2027.0 makes advice parameter binding public: aspect advices receive typed parameters instead of a MethodExecutionArgs object. That removes per-call heap allocations, boxing and casts on hot paths. Bindings are checked at build time, so mismatches fail the build rather than production.
A developer who has maintained ASP.NET Core APIs for years lists six recurring problems: scattered try/catch blocks, unbounded list queries, ignored cancellation tokens, lost UTC kinds, late config failures and unprotected login endpoints. Each comes with a suggested pattern using .NET 10 and EF Core 10, noted to work on .NET 8 with small changes.
Wolverine 6.51.3 is a durability release that fixes a run of problems in the durable inbox and outbox. A new receiver compliance suite exercised PostgreSQL, SQL Server, Marten, EF Core, RabbitMQ and SQS, and the fixes cover transactions, deduplication, retries and dead lettering. There are no breaking API changes, and the one schema addition is optional.
SharePoint Embedded guidance for moving apps to production has been updated. It covers container and tenant limits, handling throttling, narrower Graph permissions and Office co-authoring. For developers building on the Microsoft 365 platform, it offers concrete planning and security points.
Kafka consumers must pick up where they left off after a restart, crash or network failure. This article explains how committed offsets, consumer groups and manual commits govern recovery, using a C# example built on Confluent.Kafka. It also covers duplicate deliveries, poison messages and the monitoring signals that reveal a consumer quietly falling behind.
Part 4 of NimblePros' domain modeling series walks through saving C# 15 unions and closed hierarchies with System.Text.Json on the .NET 11 RC1 SDK. It shows where the built-in classifiers are enough and where a hand-made "kind" discriminator is still needed. Useful for any developer persisting polymorphic domain state to JSON.
The article explains how calling SetVaryByQuery in an ASP.NET Core output cache policy replaces the default vary-by-all-query-keys behavior. A policy that names only sort stops varying by page, so different pages can receive the same cached body. The author reproduces the bug with a small test and shows the fix.
The author compares a Cache-Control header with ASP.NET Core output caching using a handler counter. The header only instructs clients and proxies, so the handler ran on all ten calls, while output caching stored the response on the server and ran the handler once. It is a concrete warning for anyone who thinks a cache header caches on the server.
Maarten Balliauw shows how to add a Server-Timing response header in ASP.NET Core so database and external API timings appear in browser DevTools next to the network timings. The post builds a small middleware, a measurement feature that endpoints can use, and ways to reuse OpenTelemetry Activity data. It also covers gating the header so internal timings are not exposed to every caller.
The author of the C# interpreter HydraScript explains why numeric instruction indexes broke code generation and how switching to stable IAddress objects fixed it. Addresses now stay with their instructions when code is inserted, removed or replaced, so jumps keep pointing to the right place. It is a concrete case for developers building compilers or interpreters with the Visitor pattern.