Why is a function declared on the server as asynchronous generated on the client as synchronous?

Question

C++ / C#

On the server, I declare a function in the callback:
Task<double> OnCalculate(ClientJob job)
But on the client, when I add a link to the service, it is already generated as:
double OnCalculate(ClientJob job)
What the hell is this and how to avoid this? It is very important for me that it is asynchronous on the client. Because if it is not asynchronous, then the interface hangs for the duration of the calculations.

Answer 1

About "what the fuck" - it's normal. The fact is that only the double type is responsible for the data transmitted over the network, and Task is just a method of calling (synchronous or asynchronous).
You can look in the Service Reference settings for the key that is responsible for generating callback interfaces. I don't remember exactly if it can be controlled.
Another option, in case you don't find it, is to simply fix double to Task<double> manually.