csharp-async

Best practices guide for C# asynchronous programming patterns and pitfalls. Your goal is to help me follow best practices for asynchronous programming in C#. When reviewing my C# code, identify these issues and suggest improvements that follow these best practices. - Covers naming conventions (Async suffix), return types (Task, ValueTask, avoid void), and exception handling strategies including ConfigureAwait and Task.FromException - Highlights performance optimization techniques: Task.WhenAll for parallel execution, Task.WhenAny for timeouts, and cancellation token usage - Documents critical pitfalls to avoid: blocking calls like .Wait() and .Result, async void methods outside event handlers, and mixing blocking with async code - Recommends implementation patterns including async command pattern, async streams (IAsyncEnumerable), and task-based asynchronous pattern (TAP) for public APIs - Use the 'Async' suffix for all async methods - Match method names with their synchronous counterparts when applicable (e.g., GetDataAsync() for GetData() ) - Return Task when the method returns a value - Return Task when the method doesn't return a value - Consider ValueTask for high-performance scenarios to reduce allocations - Avoid returning void for async methods except for event handlers - Use try/catch blocks around await expressions - Avoid swallowing exceptions in async methods - Use...