WebSharper 2.4.35 is a bugfix release, fixing offline site generation and other important issues. See the complete list of changes.

I have been thoroughly enjoying our latest project at IntelliFactory. Me and Loïc Denuzière, the creator of FPish, are working together for the U Nebraska Medical Center on genetic visualization with HTML5/WebSharper/F#. The organism of interest is Staphylococcus aureus. We have built an interactive chart showing its genome coding sequences and a few thousand transposon insertions performed in the UNMC labs. You are welcome to play with the latest prototype. It has been fun to do some graphics and modu[...]

WebSharper 2.4, our latest F# web stack based on a F#-to-JavaScript compiler, is out today, and it is open source, with a dual licensing model: you either use AGPL + OSS exceptions or purchase a commercial license. See details at websharper.com, and source at bitbucket.org.

I discovered a memory leak in Async.StartChild and here discuss a workaround based on a Future abstraction. I noticed what appears to be a memory leak in F# standard library function Async.StartChild. This happened in a context of a socket server, where I attempted to perform socket reading and writing in parallel. It seems that memory use slowly grows and memory profiler points to some CancellationTokenSource-related objects not being released. As a non-leaking alternative, I used my own abstraction[...]

When WebSharper compiles F# to JavaScript it preserves namespaces, module and class nesting to make it easy to navigate the compiled code from JavaScript shell. Roughly speaking, A.B.C.D.E identifier in F# can be found by typing A.B.C.D.E in JavaScript. This poses a challenge: as you can imagine, emitting long qualified identifiers everywhere is not a good idea for compact code generation. To save space WebSharper 2.4 does class/module interning. The basic idea is to say L=Microsoft.FSharp.Core.ListMod[...]