-
Notifications
You must be signed in to change notification settings - Fork 184
Closed
Labels
📌 seQUESTeredLabel to indicate an item has been imported.Label to indicate an item has been imported.Pri1High priority, do before Pri2 and Pri3High priority, do before Pri2 and Pri3doc-enhancementImprove the current content [org][type][category]Improve the current content [org][type][category]dotnet-desktop/svcin-prwinforms/subsvc
Description
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/
- This article covers some thread stuff, so it could be expanded, rewritten or complimented by a new article: https://learn.microsoft.com/en-us/dotnet/desktop/winforms/controls/how-to-make-thread-safe-calls
Page URL
https://learn.microsoft.com/en-us/dotnet/desktop/winforms/forms/events?view=netdesktop-6.0
Content source URL
Document Version Independent Id
4d5076d1-338f-1d67-c72a-09e71f62c15c
Article author
Metadata
Metadata
Assignees
Labels
📌 seQUESTeredLabel to indicate an item has been imported.Label to indicate an item has been imported.Pri1High priority, do before Pri2 and Pri3High priority, do before Pri2 and Pri3doc-enhancementImprove the current content [org][type][category]Improve the current content [org][type][category]dotnet-desktop/svcin-prwinforms/subsvc