ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide how long an HttpClient should live in .NET Core. Compare typed clients via IHttpClientFactory, singleton HttpClient with handler rotation, and per‑call creation. See a concise table, trade‑offs, and concrete code examples with validation steps.
New HttpClient per request exhausts sockets; a static one ignores DNS changes. Here's how IHttpClientFactory's handler rotation fixes both, with a typed-client example and honest trade-offs.
Minimal APIs let you expose a full REST service in under 50 lines, cutting boilerplate while keeping ASP.NET Core’s routing, DI, and Swagger. This guide shows a working TODO example, trade‑offs, and when to use them.
A new HttpClient per request exhausts sockets; a static one ignores DNS changes. Here's how IHttpClientFactory's pooled, rotating handlers fix both — with a typed-client example and the singleton trap to avoid.
Misregistering service lifetimes can cause state leaks or startup crashes; this post shows how to verify and avoid common DI pitfalls in ASP.NET Core.
Learn how to toggle .NET Core app features at runtime using Azure App Configuration, with a step‑by‑step CLI and code example, plus limits and typical pitfalls.
A decision guide for .NET developers choosing between JIT, ReadyToRun, and Native AOT to balance startup speed, memory usage, and runtime flexibility.
Minimal APIs let you build lean, high‑performance web services in .NET 6/7/8 with a single file. This post explains the problem they solve, shows a working example, weighs the trade‑offs, and gives you a clear next‑step checklist.
Learn how to publish .NET Core apps as a single executable, the trade‑offs, and how to verify the result.
dotnetcore