async-patterns

To propagate CancellationToken correctly, accept and forward the token through every method in your async call chain to enable cooperative cancellation. This prevents unpropagated cancellation bugs and ensures long-running operations can be safely aborted.

Blocking on async code with .Result or GetAwaiter causes deadlocks by tying up the synchronization context. Replace synchronous waits with await-based flows to prevent deadlocks and ensure efficient asynchronous execution in .NET applications.

Use ValueTask instead of Task for async hot-path optimization when operations often complete synchronously. ValueTask reduces allocations in high-throughput scenarios, improving performance while maintaining reliable async/await patterns in .NET.

Implement timeouts by creating linked CancellationTokenSources that combine a timeout token with an existing cancellation token. This pattern allows you to enforce time limits on async operations while preserving cooperative cancellation from callers.

Design robust BackgroundService scoping by using async/await patterns, propagating CancellationToken, and avoiding async void methods. This ensures reliable background processing, proper exception handling, and cooperative shutdown in hosted services.

Avoid async void methods, blocking on Task with .Result, inappropriate Task.Run usage in request handlers, and misused ConfigureAwait. These async anti-patterns cause unobserved exceptions, deadlocks, and performance degradation in .NET applications.