The main highlight of this release is in-document template binding, a client-side feature which treats the whole document as a template to be filled.
Today we are releasing WebSharper.AspNetMvc 4.2.0, with a simplified API.
WebSharper 4.1.6 has F# query on the client and net4x builds not depending on netstandard
Reactive code can be just as clear and readable as static code with this new WebSharper.UI feature!
Tutorial for instantiating a WebSharper site and configuring it to run on AWS Lambda
This is a bugfix release for both the stable and beta branches of WebSharper.
WebSharper 4.2-beta adds support for .NET Core and compiler configuration via json
I wrote a simple template application that you can use as a base to create your own OAuth-based app.
This tutorial shows how to authenticate a WebSharper Client-Server Application with an OAuth2 service and query its API.
Consider a very typical scenario: you have a web application that serves an SPA. The SPA itself has several "pages," each with its own client-side routed URLs (think of Gmail, for instance.) Then people copy some of these URLs from their "session" and send them to others, who in turn expect to find exactly what the sender saw. Except with most SPAs, the server-side knows nothing about the URLs generated on the client and usually throws you back to some initial SPA page. Implementing this properly requires you to share all or a subset of the URLs both on the server and on the client. With WebSharper, this is easy.