Migrating to runtime async

Outbox Pattern in .NET With Postgres: Concurrent Workers vs the WAL

An API can save an order and crash before publishing the message that tells other services about it.

Exposing ABP Application Services as MCP Tools for AI Agents

Expose ABP application services as MCP tools so AI agents can use your app, with ABP’s permissions, multi-tenancy and audit logging applied automatica...

HttpClient in .NET 10 - IHttpClientFactory and Resilience

Use HttpClient in .NET 10 with IHttpClientFactory, keyed and typed clients, and AddStandardResilienceHandler, with real socket and POST retry test results.

How to Loop Through a List in C#: Every Way, Benchmarked

How to loop through and iterate a List<T> in C# with foreach, for, ForEach, Index(), and spans, plus break, continue, safe removal, and benchmarks.

Streaming Large File Uploads in Java Without Killing Your Server

Spring's @RequestPart cannot stream multipart uploads — not even FilePart. The API that actually does, and the tests that prove it.

Vertical Slice vs Clean Architecture in .NET 10 - What I Use

Vertical Slice vs Clean Architecture in .NET 10: real file counts, a decision matrix, and the pragmatic hybrid I recommend, with architecture tests.

Modernize your .NET apps for Windows Arm64 with GitHub Copilot

The GitHub Copilot upgrade agent now supports migrating .NET applications from Windows x64 or x86 to Windows Arm64. It assesses your projects, flags blockers like architecture-tied build settings and native dependencies without Arm64 binaries, then builds a migration plan. The agent updates code, dependencies, and project configuration, and builds the migrated app for Arm64, running tests when matching hardware or CI runners are available. It focuses on portability and correctness, not Arm64 performance tuning. To start, install GitHub Copilot upgrade, pick the .NET Arm64 migration scenario, and review its plan before letting it make changes.

Microsoft.UI.Reactor: a C#-first way to build WinUI apps

Microsoft.UI.Reactor là một framework C# để phát triển ứng dụng WinUI, ra mắt tại Microsoft Build 2026. Framework này giải quyết vấn đề hiệu năng khi render UI bằng cách implement virtual DOM pattern tương tự React. Thử nghiệm cho thấy UI.Render cải thiện 30% tốc độ so với WinUI truyền thống. Điều đáng học hỏi là cách tiếp cận hybrid này kết hợp ưu điểm của C# với pattern từ frontend JavaScript. Bạn nên đọc bài gốc nếu đang tìm cách tối ưu hóa hiệu năng cho ứng dụng WinUI của mình.

Microsoft.UI.Reactor mang đến cách tiếp cận đơn giản hóa và hiệu quả hơn để phát triển ứng dụng WinUI bằng C#.