Free .NET webinar Oct 30: You Should Probably Be Using IAsyncEnumerable

Free webinar: You Should Probably Be Using IAsyncEnumerable

Hey Mailwal,

A job has been running for twenty minutes. Is it working, or is it dead?

If it's a Task, you can't tell. A Task has three states: pending, completed, and faulted. A job that's almost done and a job that hung twenty minutes ago are both just "pending." So we bolt on polling loops, status endpoints, and timeouts to get back what the return type threw away.

Here's what we'll cover:

• Why long-running work isn't a value. Task gives you one result, once, at the end. A stream tells you what's happening while it happens.
• Telling "dead" apart from "stuck." I'll show an AI agent that runs two timers over its own token stream, so it knows the difference between nothing arriving and heartbeats with no real output.
• Replacing polling with push. Using IAsyncEnumerable, Channel<T>, and Server-Sent Events in ASP.NET Core to stream progress straight to the client.
• Where IAsyncEnumerable runs out. It doesn't slow down a producer that won't wait for you. We'll look at what to do about that.

You don't need any Akka.NET experience. We start with plain .NET. Bring the job nobody can tell the status of. We'll have time for questions.

Aaron