JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
See Roslyn-Detected C# Warning Classes for more information.
When an asynchronous method awaits a Task directly, continuation occurs in the same thread that created the task. Consider calling Task.ConfigureAwait(Boolean) to signal your intention for continuation. Call ConfigureAwait(false) on the task to schedule continuations to the thread pool, thereby avoiding a deadlock on the UI thread. Passing false is a good option for app-independent libraries. Calling ConfigureAwait(true) on the task has the same behavior as not explicitly calling ConfigureAwait. By explicitly calling this method, you're letting readers know you intentionally want to perform the continuation on the original synchronization context.
This check corresponds to Roslyn rule CA2007. For full rule details, see the Microsoft website: CA2007.
| Class Name | Consider calling ConfigureAwait on the awaited task (C#) |
|---|---|
| Significance | reliability |
| Mnemonic | ROSLYN.RELIABILITY.CA2007 |
| Categories | None |
| Availability | Available for C# only. |
| Enabling | Checks for this warning class are
disabled by default. To enable them, add the following WARNING_FILTER
rule to the project configuration file.
WARNING_FILTER += allow class="Consider calling ConfigureAwait on the awaited task (C#)" |
The following configuration file parameters affect checks for this warning class.
Japanese (ja)