Csharp Async

1---2name: csharp-async3description: 'Get best practices for C# async programming'4---5 6# C# Async Programming Best Practices7 8Your goal is to help me follow best practices for asynchronous programming in C#.9 10## Naming Conventions11 12- Use the 'Async' suffix for all async methods13- Match method names with their synchronous counterparts when applicable (e.g., `GetDataAsync()` for `GetData()`)14 15## Return Types16 17- Return `Task<T>` when the method returns a value18- Return `Task` when the method doesn't return a value19- Consider `ValueTask<T>` for high-performance scenarios to reduce allocations20- Avoid returning `void` for async methods except for event handlers21 22## Exception Handling23 24- Use try/catch blocks around await expressions25- Avoid swallowing exceptions in async methods26- Use `ConfigureAwait(false)` when appropriate to prevent deadlocks in library code27- Propagate exceptions with `Task.FromException()` instead of throwing in async Task returning methods28 29## Performance30 31- Use `Task.WhenAll()` for parallel execution of multiple tasks32- Use `Task.WhenAny()` for implementing timeouts or taking the first completed task33- Avoid unnecessary async/await when simply passing through task results34- Consider cancellation tokens for long-running operations35 36## Common Pitfalls37 38- Never use `.Wait()`, `.Result`, or `.GetAwaiter().GetResult()` in async code39- Avoid mixing blocking and async code40- Don't create async void methods (except for event handlers)41- Always await Task-returning methods42 43## Implementation Patterns44 45- Implement the async command pattern for long-running operations46- Use async streams (IAsyncEnumerable<T>) for processing sequences asynchronously47- Consider the task-based asynchronous pattern (TAP) for public APIs48 49When reviewing my C# code, identify these issues and suggest improvements that follow these best practices.