BeginInvoke not supported on .NET core? (PlatformNotSupported exception)

Question

I've ported a library FluentFTP to .NET standard/.NET core but the async methods use BeginInvoke within an async/await block. So its something like this:

async ConnectAsync(){
   BeginConnect();
}
void BeginConnect(){
   BeginInvoke(...)   << error at this point
}

At that point I get a PlatformNotSupported exception. What can be done to support this on .NET core?

Full info here.
Full code here: ConnectAsync, BeginConnect.

JSpot · Answer 1 · 2020-04-14T07:37:53.647

34

The motivation for implementing a "true" async method is clear, as stated by @Steven_Cleary, but sometimes you have legacy code you cannot simply make async. For those in desperate need for keeping the old interface: Use Task.Run. E.g. when you had

IAsyncResult ar = someDelegate.BeginInvoke(state, null, null);

and use properties of ar in order to see when the task is finished, you are in luck because the equivalent with Tasks is:

Task task = Task.Run(() => someDelegate(state));

The good news is that the Task class implements IAsyncResult such that you can recycle your existing code. Later when you know the delegate has finished, you might have called

someDelegate.EndInvoke();

which is neither supported by .NET Core. This can the be replaced by

task.Wait();

It eventually throws exceptions your delegate has thrown, just like EndInvoke. This worked in our migration to .NET Core.

edited Apr 14 '20 at 07:37

answered Apr 04 '19 at 13:14

JSpot

450
4
12

Notes: (a) If your delegate returns a value, `var returnValue = someDelegate.EndInvoke();` becomes `var returnValue = task.Result;` (rather than `Wait()`). (b) Task.Wait()/Result wraps exceptions in an `AggregateException`, contrary to `EndInvoke`, so it might be necessary to unwrap them. – Heinzi Feb 13 '23 at 16:11
3

To [avoid wrapping exceptions](https://web.archive.org/web/20140222150202/http:/blogs.msdn.com/b/pfxteam/archive/2011/09/28/10217876.aspx), you can use `task.GetAwaiter().GetResult()` instead of `task.Wait()`/`task.Result`. – Heinzi Feb 15 '23 at 13:24

score 29 · Accepted Answer · answered Jul 19 '17 at 14:55

Asynchronous I/O methods should not use Delegate.BeginInvoke. That's exposing a fake-asynchronous wrapper for a synchronous method that should be asynchronous in the first place. The whole design needs re-evaluation.

.NET Core does not support Delegate.BeginInvoke for very good reasons. It's possible that .NET Core 2.0 may decide to support them (because Microsoft IMO is making some poor design decisions with v2).

But back to the original problem: the solution is to do the //TODO: implement ConnectAsync as a true asynchronous method. Then it's pretty straightforward to implement BeginConnect and EndConnect as wrappers around ConnectAsync.

BeginInvoke not supported on .NET core? (PlatformNotSupported exception)

2 Answers2

Linked

Related