👀 Views: 2 💬 Answers: 1 📅 Created: 2025-06-06

async-await wpf event-handling C#

I'm deploying to production and I've been struggling with this for a few days now and could really use some help. I'm working with a frustrating scenario while using async/await in event handlers in my WPF application. I've implemented an async method to handle a button click that performs a long-running task, but it seems to freeze the UI when I click the button. Here's a simplified version of my event handler: ```csharp private async void Button_Click(object sender, RoutedEventArgs e) { await LongRunningOperation(); } private async Task LongRunningOperation() { // Simulating a long-running operation await Task.Delay(5000); } ``` Despite using await, the UI becomes unresponsive until the delay is complete. I've confirmed that the long-running operation does not run on the UI thread by checking the thread context. I also ensured that `LongRunningOperation` is awaited properly. I've tried changing the return type of the event handler to `Task` instead of `void`, but it results in a compile-time behavior since WPF event handlers must have a `void` return type. Additionally, I've considered using `ConfigureAwait(false)` to avoid capturing the context, but I’m unsure if that would resolve the scenario. Is there a recommended way to handle this situation? Should I run the long operation on a background thread instead? I want to keep the UI responsive while performing these tasks. Any insights or best practices would be greatly appreciated! What am I doing wrong? This is happening in both development and production on CentOS. I'm working with C# in a Docker container on macOS.