Async Pipelined execution does not work with Microsoft.Data.SqlClient. about dapper

[mgravell]

and why it was splitted in the first place.

to avoid the overhead of an extra async state-machine per entry

The exception seems to arise when the pair.Command is disposed and then the pair.Task is awaited.

Then I would propose a simpler fix would be to simply swap the order:

while (pending.Count != 0)
{
    var pair = pending.Dequeue();
    using (pair.Command) // dispose commands
    {
        total += await pair.Task.ConfigureAwait(false);
    }
}

This achieves the same aim, but would allow the same async state to be reused for all of the operations

[adameasten]

aa i see, dissapointed that i didn't see that solution, much better! I'll try it out locally!