Publishing NuGet packages has traditionally required one uncomfortable compromise: a long-lived API key had to exist somewhere in the delivery pipeline. Even when that secret was stored in a secure CI system, the model still relied on a credential that could be leaked, copied, mis-scoped or forgotten. Once exposed, that key could often be reused until someone noticed the incident and rotated it.
Read Blog Post
After many years of workarounds, design discussions and library-level substitutes, unions are finally becoming a first-class part of C#. The proposal in the C# language repository is no longer a distant idea. With the feature now appearing in the .NET 11 preview train as an early C# 15 capability, the direction is concrete enough to discuss in practical terms.
Read Blog Post
C# is a powerful language, but there is one road it has not yet fully paved: native discriminated union types. Developers have been working around this absence for years, typically choosing between throwing exceptions for non-exceptional paths, returning nullable values, using out parameters or layering custom wrapper classes on top of every service boundary. Each of these approaches carries a cost - in clarity, type safety or runtime efficiency.
When building cloud-native .NET applications, two goals often matter at the same time: a fast local development loop and a clean path to real Azure resources for publish mode. .NET Aspire with Azure Cosmos DB supports exactly this pattern.
Read Blog Post
The .NET team just released the first preview of .NET 11 and there is already a lot to talk about. While this is an early preview - not a release candidate - the breadth of changes touching the runtime, libraries, ASP.NET Core, Blazor, C#, the SDK and Entity Framework Core gives a clear picture of where the platform is heading. Let me walk you through the most important changes you should know about.
Read Blog Post
Large language model agents can appear intelligent while still producing unstable output across runs, contexts and tasks. In practice, this instability is rarely caused by model quality alone. The dominant factor is often missing operational structure: no explicit boundaries, no role-specific constraints, no reusable task patterns and no agreed execution policy.
Read Blog Post
Local SQL Server database files provide a pragmatic way to keep a real SQL Server engine close to the application without provisioning a full server. A LocalDB database lives in a single .mdf file (plus a log file), runs in user mode and behaves like SQL Server for most application scenarios. That makes it a strong fit for local development, integration tests and tooling that needs relational features without the overhead of infrastructure setup.
Read Blog Post
The landscape of AI development is shifting rapidly from simple chat interfaces to fully integrated, agentic workflows like the Ralph Loop . GitHub has recently introduced the GitHub Copilot SDK , a powerful toolkit that allows developers to programmatically harness the engine behind the GitHub Copilot CLI.
Read Blog Post
What if an AI agent could write code, run tests, fix errors and repeat this process autonomously until the job is done? The Ralph Wiggum Method makes this possible with a simple but powerful loop pattern. Named after the lovable Simpsons character, it embodies the philosophy: persistence wins over perfection.
Read Blog Post
Single Page Applications like React expect the server to always return index.html and let the client-side router take over. On Cloudflare Workers you can do that without custom code as long as wrangler.toml is set up correctly. This post shows the minimal configuration and why two options are essential for SPAs.