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

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.

Using MiMo V2.5 with GitHub Copilot BYOK and OpenCode Zen (Promo)

Wed, 27 May 2026 00:00:00 +0000

MiMo V2.5 is the latest reasoning and coding model from Xiaomi’s AI lab. Xiaomi positions MiMo as a general-purpose reasoning model with particular strength in code generation, structured output and tool calling. In May 2026 the model was made available through OpenCode Zen as part of a promotional offer, meaning it can be used at no cost during the promotion period.

Using OpenAI Models in VS Code with GitHub Copilot BYOK

Sun, 24 May 2026 00:00:00 +0000

GitHub Copilot’s pricing shift from flat premium request units to token-based GitHub AI Credits, scheduled for June 1, 2026, changes the economics of heavy AI usage in VS Code meaningfully. Models with large context windows, high output verbosity or intensive agent loops now have a more direct relationship between compute and cost. That makes model selection a more relevant engineering decision than it was under the older quota model.

Using Kimi K2.5 and DeepSeek V4 in VS Code with GitHub Copilot BYOK and OpenCode

Sat, 23 May 2026 00:00:00 +0000

GitHub Copilot is moving into a different cost model. GitHub announced that Copilot plans will transition from premium request units to GitHub AI Credits on June 1, 2026. Usage will be calculated from token consumption, including input, output and cached tokens, using the listed API rates for each model. This is a more direct mapping between compute usage and billing, but it also changes the economics for teams that have started to use agentic workflows heavily.

Zero-Code REST API Mocking with json-server for Angular and React

Thu, 21 May 2026 00:00:00 +0000

Frontend development often hits a practical wall early: the backend API does not exist yet, is unreachable in local environments, or is shared between multiple teams and cannot be safely modified during development. The typical workarounds - hardcoded response stubs, in-memory interceptors, or hand-rolled Express servers - all impose overhead that does not belong in the development workflow.

Cloudflare Workers with wrangler.toml: Preview URLs, production routes and SEO-safe SPA handling

Sun, 10 May 2026 00:00:00 +0000

Cloudflare Workers can separate production and preview traffic cleanly without sacrificing canonical URL control. For search visibility, that detail matters more than the mere existence of preview links. The production hostname stays singular, the preview hostname stays disposable and the Worker runtime can normalize HTML paths before duplicate URLs leak into indexing.

Azure Static Web Apps with GitHub Actions: Pull Request Preview Environments, automatic teardown and stable production URLs

Wed, 06 May 2026 00:00:00 +0000

Azure Static Web Apps has one feature that is easy to underestimate until a team starts using it seriously: pull requests can behave like first-class deployment units.

Backing Up GitHub Repositories on Synology NAS with gickup

Thu, 23 Apr 2026 00:00:00 +0000

GitHub is an operational platform, not a backup strategy. For a long time, that distinction often felt theoretical because GitHub is - usually - highly available and because Git itself already distributes history well. The gap becomes visible once repositories are treated as regulated business assets instead of convenient hosting locations.