(BTW, the API links should be working now.)

By on 1/5/2018 5:48 AM ()

Hi Giulio, thanks for these notes and welcome aboard! You should indeed have the "ASP.NET and web development" workload installed, along with the "F# language support" component (or the ".NET desktop development" workload) before you install WebSharper into your Visual Studio.

The broken API links are being looked into now, thanks for finding these.

Visual Studio never worked well with NuGet packages that include .targets files, and WebSharper is such a NuGet package. This means that if you create a new WebSharper project via "New project..." the first time, you should restore all packages, then re-open the solution for the WebSharper references to kick in. Other than this step, you shouldn't have to install WebSharper into your projects separately. WebSharper UI is a WebSharper library, so whenever you need it you should add it to your project as a regular NuGet package, unless it's there already (most of the standard templates include WebSharper UI.)

By on 1/4/2018 4:41 AM ()

Small correction: reloading a project is not needed for WebSharper to work when creating the project from an installed template. The vsix installer contains all the needed .nupkg packages files in it, so template instantiation works even when you are offline, as they are fetched from the install location of VS extensions instead of doing a NuGet package restore.

However, reloading the project is indeed needed when you want to add WebSharper packages to an existing non-WebSharper project. For the WebSharper compiler to turn on, setting WebSharper-specific project properties are also needed (at least WebSharperProject)

By on 1/9/2018 6:41 AM ()