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

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

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.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should