ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #csharp
Enable C# nullable reference types to turn potential NullReferenceExceptions into compile‐time warnings, then fix them with null‐conditional operators or explicit checks.
Sync only changed users, groups, or messages with Microsoft Graph delta queries: store deltaLinks verbatim, handle tombstones, survive token expiry, with a worked C# example.
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.
In C# 8 and later, an unconstrained generic type parameter annotated as T? produces a deferred nullability contract that the compiler cannot resolve until the type is substituted. The annotation carries different meanings depending on whether T becomes a reference type or a value type, yet the generic method body receives limited static guidance about which
The Challenge When enabling nullable reference types on an existing codebase, the compiler treats unannotated legacy libraries as 'oblivious'—assuming T? for all reference types. This suppresses warnings but erases static safety guarantees at the call boundary between annotated and unannotated code. The four-state nullable context model (annotation context a
dotnet