Skip to main content

Going from Tasks back to IAsyncResult(the Asynchronous Programming Model pattern)

There are lot’s of posts out there talking about how to go from the traditional APM approach(using the typical BeginXXX and EndXXX syntax with IAsyncResult) to the Task based approach. Probably the easiest way is by using the Task.Factory.FromAsync method.

But what if you want to do it the other way around and want to go back from a task to the APM way of working?

In my specific case I wanted to wrap the async version of ExecuteNonQuery that returns a Task<int>:

Task<int> ExecuteNonQueryAsync();

It had to be mapped to an APM implementation with the following signatures:

IAsyncResult BeginExecuteNonQuery(DbCommand command, AsyncCallback callback, object state);
int EndExecuteNonQuery(IAsyncResult asyncResult);

I started by implementing it myself but there a lot of edge cases, so I was happy to find the following extension method :

public static class ToAPMExtension
{
static Task<TResult> ToApm<TResult>(this Task<TResult> task, AsyncCallback callback, object state)
{
if (task.AsyncState == state)
{
if (callback != null)
{
task.ContinueWith(delegate { callback(task); },
CancellationToken.None, TaskContinuationOptions.None, TaskScheduler.Default);
}
return task;
}
var tcs = new TaskCompletionSource<TResult>(state);
task.ContinueWith(delegate
{
if (task.IsFaulted) tcs.TrySetException(task.Exception.InnerExceptions);
else if (task.IsCanceled) tcs.TrySetCanceled();
else tcs.TrySetResult(task.Result);
if (callback != null) callback(tcs.Task);
}, CancellationToken.None, TaskContinuationOptions.None, TaskScheduler.Default);
return tcs.Task;
}
}

The implementation of my BeginExecuteNonQuery method became:

public IAsyncResult BeginExecuteNonQuery(DbCommand command,AsyncCallback callback, object state)
{
command.ExecuteNonQueryAsync.ToApm(callback, state);
}

And the implementation of my EndExecuteNonQuery method became:

public int EndExecuteNonQuery(IAsyncResult asyncResult)
{
try
{
return ((Task<int>)asyncResult).Result;
}
catch(AggregateException ae)
{
throw ae.InnerException;
}
}

A similar solution could be found on Stephen Cleary’s blog who created a useful Helper library for async task-based programming called Nito AsyncEx.

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

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.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...