Skip to main content

Using IAsyncEnumerable with Dapper

When using IEnumerable in asynchronous context, you could not await it. With the introduction of IAsyncEnumerable it becomes possible to asynchronously iterate over a sequence of elements. It allows you to use the await keyword within the loop, which means you can perform asynchronous operations on each element as you iterate over them.

In other words, IAsyncEnumerable provides an asynchronous version of the IEnumerable interface, making it easier to work with asynchronous data streams. You can use it to represent data streams that are produced asynchronously, such as a stream of data received over a network or a series of results returned from an asynchronous database query.

I was wondering if I could use this interface with Dapper, the open source micro-ORM for .NET. It turned out that there was no IAsyncEnumerable  support available out-of-the-box but maybe we could (easily) add it ourselves?

I created the following extension method:

Here is an example on how to use it:

Don’t know if this is a foolproof implementation but maybe it can help you…

More information: Iterating with Async Enumerables in C# 8

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more