ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #csharp
Learn how to implement the async/await pattern in C# to prevent UI freezes and improve server throughput by releasing threads during I/O operations.
Learn how C# 9 records provide immutable data carriers with value‑based equality and concise with‑expressions, plus practical guidance on usage, trade‑offs, and verification steps.
Learn how to implement a thread-safe Singleton in C# using Lazy<T> to avoid race conditions and manual locking during shared resource initialization.
Avoid captive dependencies and state leaks in C# by correctly implementing ASP.NET Core DI lifetimes, enforcing trust boundaries, and using scope validation.
Stop creating unnecessary string objects. Learn how to use ReadOnlySpan<T> and slicing to eliminate heap allocations in C# parsing logic and reduce GC overhead.
Synchronization Context Capture \n In C# asynchronous programming, the await operator captures the current SynchronizationContext by default to ensure the continuation runs on the original thread. This is essential for updating UI elements in frameworks like WPF or WinForms. \n To optimize performance and avoid potential deadlocks in library code, ConfigureA
Goal Ensure that all parts of a partial class share the same accessibility modifier so that an unintentional public exposure does not occur. Constraints The current C# compiler (Roslyn) silently merges partial class parts, taking the most permissive modifier without any warning or error. This behavior can cause a type intended to be internal to become public
When deploying a C# application as a self‑contained package, I need to ensure the correct .NET runtime is bundled while also controlling which SDK version is used for building and publishing across different operating systems. The CLI chooses the latest SDK unless a global.json overrides it, and runtime roll‑forward can affect which version runs on target ma
ADO.NET utilizes connection pooling to minimize the overhead of establishing physical database connections. By default, the pool manages connections based on the exact connection string provided, and the Max Pool Size attribute defines the upper limit of physical connections allowed per pool. When an application reaches this limit and all connections are cur
dotnet