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.
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.
Microsoft has introduced Work IQ, a workplace intelligence layer that lets AI agents read and act on live Microsoft 365 and Dynamics 365 data. Developers can reach it through an MCP server, an A2A endpoint or a REST API instead of wiring up many Graph endpoints. Every request runs under the signed-in user's Entra ID identity.
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.
Bruno Capuano shows a local .NET pipeline that turns podcast audio into SRT or WebVTT subtitles. Whisper handles speech recognition and timestamps, while the s1-mini model only cleans each cue's text, so timing stays untouched. The post also covers the limits he found with long Spanish recordings.
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.
Allan Ritchie of Shiny introduced Shiny.UniversalHubs, which serves the same BLE Hubs contract over Wi-Fi as well. One hub implementation and one contract work on both transports, and the client chooses which one to prefer. For .NET MAUI developers building multiplayer or nearby-device apps, it shows a concrete way past Bluetooth's range and bandwidth limits.
Copilot Autofix for GitHub Advanced Security in Azure DevOps now runs on an agentic foundation. It proposes fixes as pull requests for code scanning alerts from third-party tools and for dependency vulnerabilities. Your team still makes the final merge decision, so the fixes need to be reviewed like any other change.
Azure Cosmos DB's Safe Key Rotation now shows the last-used timestamp for each account key and can be turned on from the Features blade in the Azure portal. Teams can confirm whether a key is still in use before regenerating it or disabling local authentication. That lowers the risk of an outage caused by rotating a key that a forgotten application still depends on.