11

I'm calling a third-party API which has a method that looks like this:

myServiceClient.Discover(key, OnCompletionCallback);

public bool OnCompletionCallback(string response)
{
    // my code
}

My challenge is, I have to call Discover because it does some work under-the-covers that I need. At the same time, I have to wait for Discover to complete before running my custom code. To further complicate matters, I can't just put my code in the OnCompletionCallback handler because I need to call the code above from a Func delegate. In short, I want to do this:

Func<SystemTask> myFunction = async () =>
{
    await myServiceClient.Discover(key);

    // my code
}

However, I can't do this because the third-party API uses a callback approach instead of an async/await approach.

Is there some way to make the callback approach work in an async / await world?

Camilo Terevinto
  • 31,141
  • 6
  • 88
  • 120
Some User
  • 5,257
  • 13
  • 51
  • 93

1 Answers1

33

If I understand you correctly you can do something like this

public Task<bool> MyAsyncFunction()
{
    var tcs = new TaskCompletionSource<bool>();

    myServiceClient.Discover("somekey", s => {
        //........
        var res = true;
        tcs.TrySetResult(res);
        return res;
    });

    return tcs.Task;
}

Now you can await MyAsyncFunction

Eser
  • 12,346
  • 1
  • 22
  • 32
  • Was just writing my comment. Exactly what I was thinking. In the end, everything is still just a delegate. +1 – TyCobb May 01 '18 at 21:01