Back to Questions
1.0k
views4
comments
Compile and return Sitelet from FSX to use in OWIN selfhost
websharpercompilerfsx

I have a sitelet which is entirely in a FSX. I am trying to compile it (using FSharp.Compiler.Service) and get the sitelet as a result to bind it to a OWIN Selfhost which lives in a console app.

My page url is http:localhost:9091/test. It works when I don't use client side code but as soon as I add client <@ Client.main() @> with Client.main() being the reference to my client side code, I get the following error when I navigate to the page:

1
2
3
4
5
6
7
8
9
10
11

System.Exception: Error in InlineControl at C:\Users\hudson.IFBUDS02\Server\var\jobs\websharper.ui.next\workspace\WebSharper.UI.Next\Doc.fs: 459.58-459.79: 
Couldn't find address for method at .$Control.WebSharper-IRequiresResources-Encode@144.Invoke(String message) 
at WebSharper.Web.InlineControl`1.WebSharper-IRequiresResources-Encode(Info meta, Provider json) 
at Microsoft.FSharp.Primitives.Basics.List.collectToFreshConsTail[T,TResult](FSharpFunc`2 f, FSharpList`1 list, FSharpList`1 cons) 
at Microsoft.FSharp.Primitives.Basics.List.collect[T,TResult](FSharpFunc`2 f, FSharpList`1 list) 
at WebSharper.Sitelets.Content.metaJson[T](Info m, Provider jP, IEnumerable`1 controls) 
at WebSharper.Sitelets.Content.writeResources[a](Env env, IEnumerable`1 controls, FSharpFunc`2 tw) 
at WebSharper.Sitelets.Content.renderHead@159.Invoke(HtmlTextWriter tw) 
at .$Page.get_Default@43.Invoke(FSharpOption`1 doctype, FSharpOption`1 title, FSharpFunc`2 writeHead, FSharpFunc`2 writeBody, HtmlTextWriter writer) 
at WebSharper.Sitelets.Content.writeBody@157.Invoke(Stream stream) 
at WebSharper.Owin.Internal.W2O.WriteResponse@164.Invoke(Task`1 obj)

Instead of pasting all the code here, I pushed it to a repo.

How can I use client side code with a Sitelet built in FSX that I compile and return in a Console app?

.

Yes, in addition to compiling with WebSharper in order to create the js files, you also need to pass the resulting metadata to the OWIN host. In a normal project, the metadata is loaded from assembly files located in binDirectory; but here since you have a dynamic assembly, it's not enough, you need to pass the metadata explicitly. In Warp, this is done here. In your case you need to call UseCustomSitelet:

1
2
3
4

appB.(*...*)
    .UseCustomSitelet(
        Options.Create(sitelet.Metadata),
        sitelet.Sitelet)

where sitelet.Metadata is asm.Info from produceScripts.

UseCustomSitelet is marked obsolete, but it's currently the only way to pass custom metadata because we haven't added it to WebSharperOptions yet. I'll fix this oversight shortly.

By on 11/24/2015 1:07 AM ()

Hi Loic, thanks a lot for the reply!

I have changed the OWIN host and pass the metadata given from the compilation of the assembly as you mentioned but I am still getting the same error when I navigate to the \test page.

1
2
3
4
5

let options = WebSharper.Owin.Options
	.Create(sitelet.Metadata)
	.WithServerRootDirectory(@"C:\Projects\SiteletFsx\SiteletFsx\bin\Debug")
    .WithDebug(true)
appB.UseCustomSitelet(options, sitelet.Sitelet) |> ignore

Am I missing something else?

By on 11/24/2015 4:11 AM ()

Ha, found it! Here you're shadowing the asm received as argument with a call to Assembly.GetCallingAssembly(). But since the current function compile is called from compileToWs, the calling assembly is Common, not F# interactive's dynamic assembly. Delete this line and you should be good.

By on 11/24/2015 6:46 AM ()

Argh... I feel so dumb. Thanks a lot Loic for taking the time to look at it!

By on 11/24/2015 1:38 PM ()

    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