Archive

Thursday, October 29, 2026
stories of the day

17stories
Fabric IQ
Business meaning for agents
KCKunal Chowdhury [email protected] (Kunal Chowdhury) 4 d ago

Microsoft Fabric IQ: ontologies for Data Agents and Operations Agents

Microsoft Fabric IQ is a new Fabric workload that maps OneLake tables, Power BI semantic models and real-time Eventhouse streams to shared business entities. Its Ontology item, currently in preview, lets Fabric Data Agents and Operations Agents work with business concepts instead of raw schemas. Read on if you are deciding whether to model business meaning before connecting LLMs to your data.

Bobcat 1.0
Readable C# specs

Writing executable specifications with Bobcat in C#

Critter Stack's new Bobcat 1.0 turns ordinary C# tests into readable executable specifications. The author starts from an existing xUnit test, adds step helpers, then covers decision tables and set verification for collections. It is a practical walkthrough for .NET teams who want reviewable tests without a Gherkin layer.

Azure SQL
Live query diagnostics
SQAzure SQL Blog Jerry Nixon 5 d ago

Azure SQL operational statistics for PostgreSQL developers

This installment of Microsoft's PostgreSQL-to-SQL field notes compares how each engine helps you diagnose slow queries. It shows which Azure SQL dynamic management views and functions expose in-flight plans, last actual plans, wait statistics and memory grants without preinstalled extensions. Developers moving data access code or troubleshooting Azure SQL performance will find the setup details useful.

AI agents
Checks before the model
DVDEV Community: #dotnet MICHAEL-MAURICE 5 d ago

Six checks an AI Telegram assistant needs before the model runs

A developer built a Telegram assistant in n8n that can send email and book meetings, with its decisions guarded by a small ASP.NET Core API on .NET 10. The post lists six checks that run before the model sees a request: chat allowlist, duplicate updates, stale messages, voice length, contact ambiguity and time zones. It is a useful checklist for any bot that triggers side effects.

Azure SDK Ekim 2026
Identity and Cosmos DB
AZAzure SDK Blog Sandeep Sen 5 d ago

Azure SDK October 2026: Azure Core, managed identity and Cosmos DB for Rust 1.0.0

The October 2026 Azure SDK release highlights Azure Core 1.63.0 for .NET, Identity updates for Python and Java, and the first stable Cosmos DB for Rust 1.0.0. The authentication changes affect how DefaultAzureCredential behaves in production. Teams on the Cosmos DB Rust preview also get concrete upgrade steps.

.NET 11
Async under the hood
HBHabr C# (ru) sproshchaev (OTUS) 5 d ago

Where Runtime Async in .NET 11 saves memory and where it doesn't

.NET 11 moves async method suspension from compiler-generated state machines to the runtime, with the JIT optimizing the boundaries between async methods. The author reruns the official benchmarks on RC2 and compares allocations, stack traces and assembly size. The gains are real in synchronous await chains and exception-heavy paths, but measurement setup changes the picture.

FluentMap 3.6
Keep old mappings working
DVDEV Community: #dotnet Rodrigo de Oliveira 5 d ago

Dapper FluentMap Is Back: What Changed from 2.0 to 3.6

After six years without a stable release, Dapper FluentMap is maintained again and version 3.6.0 adds nested mappings, property converters, isolated runtimes, analyzers and source generators. The author stresses keeping existing applications working during upgrades. The piece also covers what to check before moving from 2.0.0 and which databases are certified.

Game Boy in C#
Rebuild hardware in C#
DPdotnetpro (de) Stefan Fiedler 5 d ago

Game Boy emulation in C#, part 1: CPU, memory and registers

A new dotnetpro series walks through building a Game Boy emulator in C#. Part one covers the 16-bit address bus, the 64 KB memory map, CPU registers modeled as C# fields and properties, and the flag register. It also shows how opcodes are dispatched in a switch loop and how cycle counting keeps components in sync.

PostSharp 2027.0
Agents see the aspects
PMMetalama / PostSharp Blog Gaël Fraiteur 5 d ago

PostSharp 2027.0 gives AI coding agents the real API and build facts

PostSharp 2027.0 adds tooling that helps AI coding agents work correctly in PostSharp projects, including a plugin for Claude Code and Codex. The release also brings CLI commands that show which aspects were applied to a declaration after a build, per-message error documentation, and an aspect test framework. These are useful for .NET developers who write or maintain aspects.

EF Core
Keep tenant data apart
DVDEV Community: #efcore Zohaib Ahmad 5 d ago

Multi-tenancy in EF Core: no tenant means no rows

The author shows a multi-tenancy pattern for ASP.NET Core and EF Core that uses global query filters so each request only sees its own tenant's rows. When no tenant is set, filtered queries return nothing, which fails closed. The post also covers tenant-scoped unique indexes, limiting IgnoreQueryFilters(), and an integration test that checks cross-tenant access. It is a practical starting point for SaaS backends.

Wolverine
Handlers as pure logic
JXJasperFx (Critter Stack) Blog Jeremy Miller 5 d ago

Wolverine Best Practices Revisited: A-Frame and Handler Design

JasperFx rewrote the Wolverine best practices guide from scratch, replacing the 2023 version. The new guide centers on the A-Frame Architecture and gives concrete advice on splitting handlers, error handling, and at-least-once messaging rules. It is a practical reference for .NET teams building messaging systems with Wolverine.

OrmLite 10.4
Automatic retries on errors

Resilient Retries and Read Replicas in OrmLite

ServiceStack v10.4 lets OrmLite retry temporary database errors such as deadlocks, throttling and failovers through a single configuration line. It also adds read replica support, with read-only connections that reject writes even on the primary so replica bugs surface during development. Both features matter for any .NET app that talks to a database under load.

ServiceComposer
Typed models, no shared code

ServiceComposer: strongly typed view models without shared coupling

Mauro Servienti examines how strongly typed view models in ServiceComposer can reintroduce the coupling that ViewModel Composition is meant to remove. He proposes per-service interfaces for response models and per-service request models for decomposition, and discusses a DispatchProxy idea that would drop the concrete class. Read on for the trade-offs and deployment caveats, including property name collisions.

Feedback

Found a bug or have an idea? Your message lands straight in my inbox.

Type of message