What's new with async support for WinForms event handlers?

I’m sure I’m not the first to ask this but is there anything new with regards to WinForms event handlers implementing async?

Basically, since everything is basically done in event handlers with WinForms, the question is can I use async/await at all?

Looks like the old workaround is to return void instead of Task. But I know this can cause problems.

I know the WinForms engine was recently built for .NET 5.0/6.0. Was any thought given to this?

[KlausLoeffelmann]

We have planned this for the .NET 7 timeframe, but we also need to complete some urgent new Designer functionality, so we may reprioritize or not tackle all of those. As always: Help for from the community is highly appriciated!

https://github.com/dotnet/winforms/issues/4631 https://github.com/dotnet/winforms/issues/5917 https://github.com/dotnet/winforms/issues/5918

If you have other things in mind, you’d find important, please file an issue!

[KlausLoeffelmann]

Well, depending events can be problematic, since async void are fire and forgets. So, if you have for example a Processing and a Processed event, where Processing is supposed to be blocked on the consumer-side, you might be ending up with firing both in succession, since Processing would not be (a)waiting for the consumer-side to be finished, since it is a fire and forget. So, invoking that event should be done asynchronously and awaited.