kerams

I think my current proposed solution is a combination of 1 and 2. On the server side, the Remoting API would support `Task` returning functions, but internally there are still...

@Thorium, the type spoofing only happens in the context of Fable (because, as you noted, it has no support for tasks - you'd have to open a separate issue for...

> Typical webserver role is to fetch a resource from task-based asynchronous resource like "give me an item from database" or "read me a file". That's not an asynchronous workflow....

I see `Result: 0001-01-01 01:12:00 +01:12` in the REPL (I'm GMT+1, so this looks correct, even though JS adds what might be 12 leap minutes, while .NET does not).

This is something I was looking into in the past. I don't recall there being any blockers, but JSON serialization is baked in the request side of things a little...

You can find what's changed between versions on the Release notes tab on Nuget, but right now we do not maintain accumulative changelog files for each package.

Isn't the problem simply the fact that there's [support only for 1 and 2 parameter functions](https://github.com/Zaid-Ajaj/Fable.Remoting/blob/2d88a987d68f69ab4172c8563f3401a40dbe1e4d/Fable.Remoting.Server/Documentation.fs#L13-L38)? I guess it's not possible to generalize this with an expression taking functions with...

Time to fork it again it would seem.

Neither of your solutions or a combination thereof worked for me. All I got was a different error instead. ``` Script is not valid: unknown (1,0)-(1,0): Error FS0193: The module/namespace...

None, net6.0, netstandard2.1 result in the error above. netstandard2.0 results in the OP error.