Support for Async controller methods

[khorvat]

Hi,

do you plan to add support for async controllers ?

btw great library.

Thanks

[ploeh]

'Plan' is such a big word, but I've considered it :)

I think it's a good idea.

[khorvat]

Just to be clear, if I pass in the async method without awaiting or invoking result your code works, but VS is raising warnings all over the place.

So if there is a room in your 'plan' it would be nice to kill those warnings.

Thanks

On Sep 18, 2013, Mark Seemann notifications@github.com wrote:

'Plan' is such a big word, but I've considered it :)

I think it's a good idea.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

-- Sent from my Android phone with K-@ Mail. Please excuse my brevity.

[ploeh]

The problem with adding support for this right now is that in order to do that, I'd have to upgrade Hyprlinkr to target .NET 4.5, and right now it only supports .NET 4.0.

However, the up-coming Web API 2 (version 5.0.0 AFAICT) seems to support only .NET 4.5, so it seems reasonable to upgrade Hyprlinkr at that time too. After that, I'll add support for async controllers.

[ploeh]

I found a way to implement this on .NET 4.0, so the latest version of Hyprlinkr (0.9.9) now supports async Controller methods like this:

Uri actual = linker.GetUriAsync((AsyncController c) => c.Get(id)).Result;

[khorvat]

Great, I'll give it a try and let you know how it goes.

Thanks

[khorvat]

Just to confirm that everything is working as expected - without warnings ;) ... thanks again.

[ploeh]

Thank you for reporting back :)

[barbosatek]

AsyncController is MVC specific, do you have any workaround for WebAPI?

[khorvat]

Hi @barbosatek, the above example is working in WebAPI so could you give us an example if the issue you have ?

[ploeh]

AsyncController is MVC specific, do you have any workaround for WebAPI?

Discussion moved to #42