-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async event handlers #1406
Labels
doc-enhancement
Improve the current content [org][type][category]
dotnet-desktop/svc
Pri1
High priority, do before Pri2 and Pri3
📌 seQUESTered
Label to indicate an item has been imported.
winforms/subsvc
Comments
PRMerger20
added
dotnet-desktop/svc
winforms/subsvc
Pri1
High priority, do before Pri2 and Pri3
labels
Jun 21, 2022
Thank you for this feedback! We'll look at getting this issue prioritized. |
adegeo
added
the
doc-enhancement
Improve the current content [org][type][category]
label
Jun 27, 2022
sequestor
bot
added
📌 seQUESTered
Label to indicate an item has been imported.
and removed
🗺️ reQUEST
Trigger label to import an issue into Quest
labels
Jun 14, 2024
adegeo
added
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Aug 1, 2024
dotnet-bot
removed
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Aug 1, 2024
adegeo
added
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Aug 4, 2024
dotnet-bot
removed
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Aug 4, 2024
adegeo
added
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Aug 4, 2024
dotnet-bot
removed
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Aug 4, 2024
dotnetrepoman
bot
added
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
and removed
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
labels
Nov 5, 2024
dotnetrepoman
bot
removed
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
label
Nov 5, 2024
dotnetrepoman
bot
added
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
and removed
🗺️ mapQUEST
Only used as a way to mark an issue as updated. RepoMan should instantly remove it.
labels
Dec 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
doc-enhancement
Improve the current content [org][type][category]
dotnet-desktop/svc
Pri1
High priority, do before Pri2 and Pri3
📌 seQUESTered
Label to indicate an item has been imported.
winforms/subsvc
Type of issue
Other (describe below)
Description
There should be documentation about how async event handlers work, best practices and pitfalls.
One issue is this documentation from DevExpress that instructs developers to use
.GetAwaiter().GetResult();
. This which would likely cause deadlocks, and I wanted to point DevExpress to documentation that shows them why this is bad, but cannot find anything official on why it is bad or what the workarounds may be.There are countless more SO posts about various async issues when using WinForms.
Added by adegeo:
Good reference is at https://devblogs.microsoft.com/dotnet/configureawait-faq/
Page URL
https://learn.microsoft.com/en-us/dotnet/desktop/winforms/forms/events?view=netdesktop-6.0
Content source URL
https://github.com/dotnet/docs-desktop/blob/main/dotnet-desktop-guide/net/winforms/forms/events.md
Document Version Independent Id
4d5076d1-338f-1d67-c72a-09e71f62c15c
Article author
@adegeo
Associated WorkItem - 291113
The text was updated successfully, but these errors were encountered: