WebSharper client-server: Owin or not Owin?

[Tarmil]

Here is a question regarding the use of Owin in the WebSharper templates.

• For the SPA template: I removed all references to Owin in PR #12. The reason is that the purpose of the SPA template is to serve a plain HTML page without any server side, so there is no reason to have any use of Owin.
• For the client-server template: as it stands, there is Owin code in the template, but it is completely unused, because Web.config points to WebSharper's ASP.NET HttpModules instead. I see three ways to go to make the project nicer:
  • Keep the HttpModule-based project and remove all Owin code;
  • Keep an IIS-hostable project, but use Microsoft.Owin.Host.SystemWeb instead of the HttpModules;
  • Switch to a self-hosted executable using Katana / Microsoft.Owin.Host.HttpListener.

[Krzysztof-Cieslak]

Personally, I would like to have IIS-hostable Owin based project. But that's just my personal preference. No idea which solution is most used / popular.

[Tarmil]

I just tried to implement it, and hit this bug. It will likely need a fix in WebSharper.Owin itself.

[Tarmil]

Found and fixed the bug, we'll be able to switch to Owin.Host.SystemWeb as soon as the next WS.Owin release hits nuget.

[Krzysztof-Cieslak]

Amazing. So update PR after new nuget is released, let me know, and then I'll merge all changes.

[Krzysztof-Cieslak]

@Tarmil, any progress with this? Do You have any idea when it will be released?

[Tarmil]

I've just come back to this, I have a version that is working except for one detail: because of this issue, it doesn't work when compiling for F# 3.1 on VS2015.