Stephen Cleary

The token is there so that your task is aware of when ASP.NET is trying to shut down the AppDomain. The AspNetBackgroundTasks library will wait for your task to complete...

This isn't possible directly, since `AsyncDiagnostics` must use something like `PostSharp` or `Fody`, neither of which support `netcoreapp` yet. It looks like `PostSharp` has preview-level support for that target, so...

PostSharp's support is still in preview. I haven't had a chance to play with it yet.

I haven't had a chance to run this yet, but that is what I suspected. This isn't a deadlock, but it is the result of thread pool exhaustion. All the...

Yes, this is actually a known problem (though it didn't have a GH issue before). In fact, this is exactly the reason why AsyncEx v5 is still in prerelease. One...

No; the problem can be caused by either synchronous or asynchronous APIs when the thread pool is saturated. At the core, both sync and async lock APIs require a thread...

Making the continuations synchronous has its own problems. For a given TaskCompletionSource, its continuations can either be forced-asynchronous (used by v5) or unspecified (used by v4). Synchronization primitives in v4...

Just to clarify, the synchronous vs asynchronous continuations that I'm talking about are only when there is a continuation, so from the end-user's perspective this only applies when the await...

That is very interesting. Particularly since the thread pool has special dedicated I/O threads so that the limited thread injection rate *shouldn't* affect that kind of scenario. But in reality,...

@waynebrantley Yes, that's a fine workaround while this bug is still in AsyncEx.