Hi, I'm Ben. I use code to solve your problems. on BEN ABT

Problem Details in ASP.NET Core and .NET 11

Mon, 05 Oct 2026 00:00:00 +0000

builder.Services.AddProblemDetails() registers infrastructure. It does not create an error contract.

An ASP.NET Core request can fail during binding, validation, authentication, authorization, endpoint execution, exception handling, routing or rate limiting. Without one design, those paths return different media types, identifiers and amounts of detail. Clients still need special cases even though some responses happen to use the ProblemDetails class.

Resilience in .NET with Microsoft.Extensions.Resilience

Mon, 21 Sep 2026 00:00:00 +0000

Retries are the most visible resilience strategy and the easiest one to misuse. Repeating a failing call can recover from a short network problem. It can also multiply load, repeat a write and keep working long after the caller has left.

What Matters in ASP.NET Core 11

Mon, 14 Sep 2026 00:00:00 +0000

ASP.NET Core 11 has no single feature that fundamentally changes how web applications are built. That is not a criticism. Mature frameworks improve by removing custom infrastructure, tightening defaults and making common behavior cheaper or easier to observe.

Migrating Semantic Kernel Agents to Microsoft Agent Framework

Mon, 07 Sep 2026 00:00:00 +0000

Microsoft Agent Framework is the successor to the agent capabilities in Semantic Kernel and AutoGen. That statement is easy to misread as “replace the package and rename a few classes.” The migration is more architectural than that.

Building Production MCP Servers with ASP.NET Core

Mon, 31 Aug 2026 00:00:00 +0000

An MCP server can look deceptively small. A package is installed, a method receives an attribute and ASP.NET Core maps an endpoint. That is enough for a demonstration. It is not enough for a server that is allowed to read company data, call internal services or change business state on behalf of an AI application.

Telemetry, Logging and Auditing in .NET: Designing the Right Data Path

Mon, 24 Aug 2026 00:00:00 +0000

Telemetry, logging and auditing are often implemented through the same API because all three produce timestamped records. That similarity is superficial. They answer different questions, tolerate different failure modes and require different storage contracts.

Automatic TTL in Azure Cosmos DB with .NET

Mon, 17 Aug 2026 00:00:00 +0000

Temporary data is easy to create and surprisingly difficult to remove reliably. Sessions, idempotency keys, import buffers, transient integration responses, processed-message markers and short-lived audit records all have a natural end of life. Without an explicit lifecycle, they remain in the database, increase storage and indexing cost and eventually make ordinary queries operate over data that no longer has business value.

Custom Password Hashing in ASP.NET Core: A Versioned, Upgradeable Design

Mon, 10 Aug 2026 00:00:00 +0000

Applications that do not use ASP.NET Core Identity still need a disciplined password-storage design. This often leads to a requirement phrased as “password encryption.” That phrase is dangerous because encryption is reversible: an application holding the key can recover every password. Password storage needs a deliberately one-way, slow derivation function instead.

MCP C# SDK 2.0: Stateless HTTP, Interactive Tools and a Practical Migration Path

Mon, 03 Aug 2026 00:00:00 +0000

The 2.0 release of the official Model Context Protocol (MCP) C# SDK is more than a version increment. It implements the 2026-07-28 MCP specification revision, which changes the default shape of MCP over HTTP. The protocol now favors independent, self-describing requests over a connection-scoped session, while still supporting interactive workflows that need more than one exchange.

Handle time correctly in .NET: TimeProvider

Mon, 27 Jul 2026 00:00:00 +0000

Time is an external dependency. That may sound unusual at first because DateTime.UtcNow is available anywhere without configuration. This convenience becomes a problem as soon as business rules depend on the current moment: expired invitations, time-limited tokens, cancellation windows, rate limits, background jobs and reminders.

Run Hono on Azure Static Web Apps: managed Functions APIs for static frontends

Sun, 19 Jul 2026 00:00:00 +0000

Azure Static Web Apps is primarily a host for static frontend assets, but it can also deploy a small HTTP API alongside the frontend. That API is implemented as an Azure Functions application and is exposed through the same site under the fixed /api path. Hono fits this model well when a web application needs a focused JSON API without introducing a separately operated container or web host.

Problem Details in ASP.NET Core and .NET 10

Wed, 15 Jul 2026 00:00:00 +0000

Error responses are part of an API contract. Still, many systems grow them incidentally: one endpoint returns { "error": "not found" }, another returns an array of validation errors, a gateway adds its own structure and an unexpected exception ends up as another JSON shape. That is inconvenient for people and brittle for client applications.

Using MeterListener with the new .NET 11 MemoryCache metrics

Tue, 14 Jul 2026 00:00:00 +0000

.NET 11 adds a small but useful improvement to the built-in observability story: MemoryCache can now publish OpenTelemetry-compatible metrics directly through System.Diagnostics.Metrics. That makes cache behavior visible without adding a custom wrapper around every Get, Set and Remove call.

Run Hono on Azure: Container Apps, Functions, App Service and AKS compared

Sun, 12 Jul 2026 00:00:00 +0000

Hono is often associated with Cloudflare Workers and for good reason. Its small routing model, Web Standard API surface and direct fetch integration make it a natural fit for edge runtimes. That association can obscure a more useful fact: Hono is not tied to Cloudflare. The same application core can run on Azure when the runtime-specific edge is kept separate from routes and business logic.

Top 10 recommendations for .NET developers working with Azure Cosmos DB

Fri, 10 Jul 2026 00:00:00 +0000

Azure Cosmos DB has a habit of exposing architectural weaknesses very early. Classic data-access patterns that work perfectly fine with relational databases often become expensive, noisy and operationally awkward once request units (RUs), partitioning and cross-partition query fan-out come into play.

How to migrate .NET versioning from x.x.x.x to SemVer

Sun, 05 Jul 2026 00:00:00 +0000

Many long-lived .NET repositories did not start with semantic versioning. They grew up with major.minor.build.revision, often set in AssemblyInfo.cs, sometimes mixed with wildcard auto increment, sometimes duplicated across several projects and sometimes quietly diverging over the years.

Modern versioning for ASP.NET Core and web apps and how to produce idempotent artifacts

Fri, 03 Jul 2026 00:00:00 +0000

ASP.NET Core applications are usually released often enough that versioning stops being a documentation concern and turns into delivery infrastructure. Once an application moves through CI, staging, production, containers, rollback procedures and incident response, the version number is no longer just a label. It becomes part of the operational model.

Modern versioning for .NET desktop apps and how to produce idempotent artifacts

Tue, 30 Jun 2026 00:00:00 +0000

Desktop software makes versioning visible in a way that web systems often do not. A backend can hide a surprising amount of release machinery behind its platform. A Windows executable cannot. Explorer exposes file versions, installers compare product versions, update channels make decisions based on package identity and support usually starts with a screenshot from an About dialog.

Modern versioning for .NET apps and libraries and how to produce idempotent artifacts

Fri, 26 Jun 2026 00:00:00 +0000

Versioning stays invisible right up to the point when it fails. A package has to be reissued, a support case depends on one exact binary or staging and production turn out to run artifacts from the same commit that do not quite match. At that moment the version number stops being release-note decoration and becomes engineering data.

Local Aspire Development with Azure Cosmos DB and the Preview Emulator

Wed, 24 Jun 2026 00:00:00 +0000

Distributed applications tend to feel straightforward until a real cloud dependency enters the picture. Azure Cosmos DB is a good example. In Azure, the preferred model is usually clear: the application should connect without secrets and authenticate through Managed Identity. Local development has different constraints. There is no managed identity attached to a machine in the same way, but the application still needs a reachable endpoint, credentials, startup ordering and a database that exists before the first request reaches repository code.