A long, practical walkthrough of ASP.NET Core authentication and authorization on .NET 10: which mechanism fits which caller, where teams leave holes such as missing resource-level checks, and what to verify before going to production.
A production write-up on rate limiting and resource governance for MCP orchestration servers, where a single tenant's burst can exhaust shared LLM token quota and starve everyone else. It compares the common limiter algorithms and lands on per-tenant token buckets with Redis-backed state and quota-aware refill rates.
Saving a lead and then calling Odoo means two writes that can each fail on their own. Anas Amin describes a transactional outbox where the lead and a message describing it commit together, and a Hangfire job delivers the message later. Leased claims, error classification, dead-lettering and idempotent Odoo writes carry the rest of the design.
A write-up on Tilly POS, a multi-branch point-of-sale built with ASP.NET Core 10, EF Core and SQL Server, explains how three costly failures were designed out: double charges, half-written sales and overselling. The fixes are practical: idempotency keys backed by a unique index, one transaction per sale, and a single conditional UPDATE for stock. Useful for any .NET service that moves money or inventory.
Reading the request body in logging middleware can leave the endpoint handler and model binding with an empty body. The author reproduces the problem with a 61-byte JSON POST and shows how EnableBuffering plus a position reset fixes it. A pitfall every ASP.NET Core developer who logs payloads should know.
This beginner guide explains GraphQL schemas, queries, mutations and resolvers and builds a working endpoint with GraphQL.NET on ASP.NET Core and .NET 10. It compares the same product read with a REST endpoint and shows how validation errors come back as HTTP 200 with an errors array. Useful for .NET teams weighing GraphQL, especially the server-side duties it adds.
This walkthrough shows how to move a tool-using ASP.NET Core agent from Semantic Kernel to Microsoft Agent Framework step by step. The Kernel-centered model gives way to IChatClient, AIAgent and AIFunctionFactory. It is a practical plan for teams already running Semantic Kernel agents.
A developer measured that favicon and robots.txt requests in ASP.NET Core walk the whole middleware chain like any API call. He shows how MapShortCircuit and ShortCircuit() answer those routes before the chain runs, with a counter proving zero middleware executions.
The author shows how to test the 404 branch of a minimal API endpoint by calling the handler directly instead of booting WebApplicationFactory. Typed result unions such as Results<Ok<T>, NotFound> make the return type a compiler-checked contract. The approach gives fast, readable unit tests, while the author keeps a thin layer of integration tests for routing, binding and middleware.
How should a warehouse order API refuse illegal state changes, short stock, stale ETag writes and malformed JSON? The author builds a pick-pack-ship demo on .NET 10 Minimal APIs and EF Core 10, mapping each refusal to a specific status code, such as 409, 412 and 400. He also explains why an exact retry should return 200 instead of an error. A useful guide for anyone designing workflow endpoints.
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.
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.