Back to Questions
709
views5
comments
Some RPC calls are broken
websharperrpc

I have a number of rpc calls in my app. Most of them work...but a few don't...

Here's an example of one that doesn't. Any ideas?

1
2
3
4
5
6
7
8
9
10
11
12

	module Farm =
      [<Rpc>]
      let  rpc_foo() = async { return "mooo" }

	[<JavaScript>]
	module Test_Farm =
    	let AddAllTests() =
        	async {
            	let! x = Farm.rpc_foo() 
                // returns x = {"item":{"f":{"builder@":{}},"x":null}}
                
        	} |> Async.Start
.

Hello!

Quite possibly your errors are caused by the browser caching the JavaScript files. WebSharper generates identifiers for Rpc functions, which can change during recompile if you have added/removed some, so your cached .js is calling the wrong Rpc endpoint. Try pressing Ctrl+F5 in your browser tab.

Please report if this has not solved your issue, thanks!

By on 4/12/2016 6:05 AM ()

I think I figured it out.
For some reason, some dlls were compiled with FSharp.Core 4.3.0.0 and others with 4.4.0.0. That problem went away when I changed the errant project to 4.3.

BTW: What version of Fsharp.Core does W# recommend?

By on 4/12/2016 10:09 AM ()

Thanks for the reply, that makes sense too, probably some incompatibility in FSharpAsync between 3.0 and 4.0. I have tried to reproduce your bug with a WS lib+sitelets projects (lib defining the Rpc), but worked for me in all configurations.

WebSharper should support any FSharp.Core 3.0+ as base libraries are compiled using that, but those don't define any Rpc methods that would be invoked dynamically. So safest route is to use the same FSharp.Core version for all projects having Sitelets or Rpc definitions.

By on 4/12/2016 11:32 AM ()

I don't know if this helps reproducing the bug but looking at the dlls. I noticed, the 4.4 version had a Attributes.RemoteAttribute on the rpc method, but 4.3 method did not.

By on 4/12/2016 1:35 PM ()

Hey András,

Thanks for the reply. I tried refreshig the cache on various browsers and machines and they all had the same bug.

By on 4/12/2016 9:22 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper