CoreWF VS wcf

Wonder how does it compare to https://github.com/UiPath/CoreWF

https://github.com/UiPath/corewf

Thanks, I even found .NET 5 port, might look up for this :)

https://github.com/dotnet/wcf/issues/4887

Technically speaking WCF is quite a bit more than SOAP, I think this might be a good overview of what people used it for (or maybe use it even now).

This article is wrong. It's hard to write and requires some out of the box thinking, but it's doable. You can see my implementation here. You can't easily implement cancellability though as you can't reset the state after an await as any changes you make will happen in a copy of the Execution Context. It could be done with a custom awaiter which chains a delegate to run before the await continuation so you can reset state on the callers ExecutionContext, but I didn't need that so didn't put the effort in.

MTOM on the client is now in code review in this Pull Request. After that's merged, I'll try to find time to port it to CoreWCF in the next month.

Next in my todo list is to add support for WCF, using CoreWCF. Long term, my goal is to also support GraphQL, SignalR, ODAta and WebSockets

There is another tool xscgen, that does not collapse container types and gets all the "inner types" correct but does not generate the Input/Output types or the client interface and client. dotnet-svcutil has another bug that prevents it from reusing external types.

There is a bug in dotnet-svcutil produces incorrect types and/or annotations when collapsing SOME pure container types into jagged arrays. dotnet-svcutil does not have the option to skip collapsing. During the contract implementation phase, which happens at runtime before the first request (ugh!), the code created viaRefEmit clashes with what the annotations specify and that exception is thrown.

I thought that wcf client exists for core? https://github.com/dotnet/wcf