Skip to content

Commit

Permalink
Changing //websharper.com/blog-entry/* links to relative paths within…
Browse files Browse the repository at this point in the history
… this folder (to .md files).
  • Loading branch information
granicz committed Sep 9, 2020
1 parent ca9aff9 commit abc1f34
Show file tree
Hide file tree
Showing 15 changed files with 29 additions and 29 deletions.
2 changes: 1 addition & 1 deletion user/denuziere/20150109-cloudsharper-0-9-25-released.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,6 @@ identity: "4156,77621"
---
We just released a new version of CloudSharper alpha, 0.9.25. This version updates the CloudSharper interface and the project templates to the latest version of WebSharper 3.0.

You can of course keep working on projects using older versions of WebSharper. If you want to update your projects, simply update the NuGet packages for WebSharper and any extensions you are using, and follow [this guide](http://websharper.com/blog-entry/4155) to upgrade your code.
You can of course keep working on projects using older versions of WebSharper. If you want to update your projects, simply update the NuGet packages for WebSharper and any extensions you are using, and follow [this guide](/user/denuziere/20150108-websharper-3-0-8-alpha-published.md) to upgrade your code.

Happy coding!
2 changes: 1 addition & 1 deletion user/denuziere/20150318-websharper-3-0-rc-released.md
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,6 @@ After that, here is a peek at what you can expect from future releases:
* TypeScript declarations: we will be stabilizing the support for outputting `.d.ts` declarations for generated JavaScript modules, which was an experimental feature so far.
* F# 4.0 support: as soon as F# 4.0 is finalized, we will provide proxies for the extended standard library.
* Source mapping: we will improve the support for [source maps](//websharper.com/blog-entry/4146), in particular reduce the need for many-to-many mapping which several browsers have trouble with.
* Source mapping: we will improve the support for [source maps](//user/jankoa/20141216-websharper-3-0-3-alpha-released.md), in particular reduce the need for many-to-many mapping which several browsers have trouble with.
Happy coding!
2 changes: 1 addition & 1 deletion user/denuziere/20150521-cloudsharper-0-9-31-published.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ categories: "cloudsharper,fsharp,web,websharper"
abstract: "This release updates CloudSharper to use WebSharper 3.1."
identity: "4392,79545"
---
This release of CloudSharper 0.9.31.0 brings it on par with [WebSharper 3.1](http://websharper.com/blog-entry/4372). CloudSharper itself uses WebSharper 3.1, and the web project templates are also updated to reference WebSharper 3.1.6.
This release of CloudSharper 0.9.31.0 brings it on par with [WebSharper 3.1](/user/denuziere/20150523-websharper-3-1-published.md). CloudSharper itself uses WebSharper 3.1, and the web project templates are also updated to reference WebSharper 3.1.6.

You can of course still use CloudSharper to work on WebSharper 3.0 projects, but we nevertheless recommend that you update your projects to WebSharper 3.1.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ identity: "4423,79893"
---
As its name suggests, UI.Next was created to be the next-generation standard library for UI programming in WebSharper. As a consequence, as of WebSharper 4.0, **UI.Next will be merged into WebSharper itself** under a less "codenamey" moniker that we haven't decided yet. It will completely obsolete the current Html.Client and Html.Server.

The [recently released version 3.4](http://websharper.com/blog-entry/4422/websharper-3-4-released) prepares the terrain for this merger. It streamlines the embedded markup syntax, introduces server-side capability and adds client-side functionality.
The [recently released version 3.4](/user/denuziere/20150803-websharper-3-4-released.md) prepares the terrain for this merger. It streamlines the embedded markup syntax, introduces server-side capability and adds client-side functionality.

## Streamlined syntax

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ categories: "cloudsharper,templates,websharper"
abstract: "To match yesterdays's official WebSharper 3 release, we are following up with a CloudSharper update, version 0.9.30. Most importantly, this release comes with updated WebSharper 3 project templates and the new UI.Next project template to make it easy to try out WebSharper 3 online."
identity: "4324,79283"
---
To match yesterdays's official [WebSharper 3 release](http://websharper.com/blog-entry/4323), we are following up with a [CloudSharper](http://cloudsharper.com) update, version 0.9.30. Most importantly, this release comes with **updated WebSharper 3 project templates** and the new **UI.Next project template** to make it easy to try out WebSharper 3 online.
To match yesterdays's official [WebSharper 3 release](/user/jankoa/20150416-websharper-3-0-released.md), we are following up with a [CloudSharper](http://cloudsharper.com) update, version 0.9.30. Most importantly, this release comes with **updated WebSharper 3 project templates** and the new **UI.Next project template** to make it easy to try out WebSharper 3 online.

Other changes and enhancements in this release are:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,10 @@ This sequence is more complicated than it needs to be because it has to work aro
Armed with that, we quickly put together a similar deployment setup for WebSharper client-server apps (other types of WebSharper apps are equally possible.) This has the obvious advantage that:

* It uses WebSharper, so you can add **client-side** (e.g. JavaScript) **functionality** as well and **write it in F#**.
* It produces an ASP.NET app that serves fine in Azure **without the need to run a separate server process** like Suave.io (although you can also create [OWIN-based self-hosted WebSharper applications](http://www.websharper.com/blog-entry/4098) and run them as in Scott's scenario.)
* It produces an ASP.NET app that serves fine in Azure **without the need to run a separate server process** like Suave.io (although you can also create [OWIN-based self-hosted WebSharper applications](/user/granicz/20141113-self-hosted-websharper-application-template-available.md) and run them as in Scott's scenario.)
* It no longer needs FAKE to compile F# apps or run F# scripts.

Loic blogged the technical details in his [WebSharper: From Zero to an Azure-deployed Web Application](http://websharper.com/blog-entry/4367) article, using a WebSharper implementation/clone of the "2048" game. I also put together a simpler template that you can use for client-server applications, and it's available in...
Loic blogged the technical details in his [WebSharper: From Zero to an Azure-deployed Web Application](/user/denuziere/20150512-websharper-from-zero-to-an-azure-deployed-web-application.md) article, using a WebSharper implementation/clone of the "2048" game. I also put together a simpler template that you can use for client-server applications, and it's available in...

## this [GitHub](https://github.com/intellifactory/ClientServer.Azure) repository

Expand Down
2 changes: 1 addition & 1 deletion user/granicz/20150615-introducing-websharper-warp.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ do Warp.RunAndWaitForInput(MySite) |> ignore

### Adding client-side functionality

Warp applications can easily incorporate client-side content and functionality, giving an absolute edge over any web development library. The example below is reimplemented from [Deploying WebSharper apps to Azure via GitHub](http://websharper.com/blog-entry/4368), and although it omits the more advanced templating in that approach (which is straightforward to add to this implementation), it greatly simplifies constructing and running the application.
Warp applications can easily incorporate client-side content and functionality, giving an absolute edge over any web development library. The example below is reimplemented from [Deploying WebSharper apps to Azure via GitHub](/user/granicz/20150515-deploying-websharper-apps-to-azure-via-github.md), and although it omits the more advanced templating in that approach (which is straightforward to add to this implementation), it greatly simplifies constructing and running the application.

```fsharp
module Server =
Expand Down
2 changes: 1 addition & 1 deletion user/granicz/20150804-introducing-try-websharper.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Here, you are opening `WebSharper.Html.Client` for accessing client-side HTML fu

#### Using `WebSharper.UI.Next`

If you followed our [recent announcements for WebSharper 3.4](http://websharper.com/blog-entry/4422/websharper-3-4-released), you will likely prefer to do the above via the more flexible [reactive HTML language](http://websharper.com/blog-entry/4423/websharper-ui-next-3-4-the-new-html-syntax) introduced via UI.Next. Here is how that goes:
If you followed our [recent announcements for WebSharper 3.4](/user/denuziere/20150803-websharper-3-4-released.md), you will likely prefer to do the above via the more flexible [reactive HTML language](/user/denuziere/20150803-websharper-ui-next-3-4-the-new-html-syntax.md) introduced via UI.Next. Here is how that goes:

```fsharp
open System
Expand Down
2 changes: 1 addition & 1 deletion user/granicz/20150806-new-websharper-templates.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ categories: "templates,f#,websharper"
abstract: "The recent release of WebSharper 3.4 also brought an update to most of the project templates shipped for Visual Studio, MonoDevelop, and Xamarin Studio."
identity: "4425,79908"
---
The [recent release of WebSharper 3.4](http://websharper.com/blog-entry/4422/websharper-3-4-released) also brought an update to most of the project templates shipped for Visual Studio, MonoDevelop, and Xamarin Studio.
The [recent release of WebSharper 3.4](/user/denuziere/20150803-websharper-3-4-released.md) also brought an update to most of the project templates shipped for Visual Studio, MonoDevelop, and Xamarin Studio.

As a quick glance, here is the template client-server (both UI.Next and the older Html type) application, with two simple pages (Home and About), demonstrating how to use master templates and how to make client-server calls.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ categories: "trywebsharper,f#,websharper"
abstract: "Just four days ago we released Try WebSharper, and here we go with the first feature enhancement: embedding snippets. A huge thanks to Don Syme for suggesting it."
identity: "4426,79915"
---
Just [four days ago](http://websharper.com/blog-entry/4424/introducing-try-websharper) we released [Try WebSharper](http://try.websharper.com), and here we go with the first feature enhancement: embedding snippets. A huge thanks to [Don Syme](https://twitter.com/dsyme) for [suggesting it](https://twitter.com/dsyme/status/628624300661149696).
Just [four days ago](/user/granicz/20150804-introducing-try-websharper.md) we released [Try WebSharper](http://try.websharper.com), and here we go with the first feature enhancement: embedding snippets. A huge thanks to [Don Syme](https://twitter.com/dsyme) for [suggesting it](https://twitter.com/dsyme/status/628624300661149696).

Each snippet and example now has an Embed tab, giving you the links or the HTML code for embedding it:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ The previous HTML support (`Html.Client` and `Html.Server`) has moved to a [sepa

### WebSharper + Suave template

Next to the recent [WebSharper.Suave announcement](http://websharper.com/blog-entry/4556/announcing-websharper-suave), WebSharper 3.5 now also ships a new project template for Visual Studio, MonoDevelop, and Xamarin Studio for running WebSharper applications on [Suave](http://suave.io). This template implements the standard client-server WebSharper "sample" application, and is easy to modify to fit your needs for any full-stack F# web application running on Suave.
Next to the recent [WebSharper.Suave announcement](/user/denuziere/20151001-announcing-websharper-suave.md), WebSharper 3.5 now also ships a new project template for Visual Studio, MonoDevelop, and Xamarin Studio for running WebSharper applications on [Suave](http://suave.io). This template implements the standard client-server WebSharper "sample" application, and is easy to modify to fit your needs for any full-stack F# web application running on Suave.

![](http://i.imgur.com/sTlLbObl.png)

Expand Down
Loading

0 comments on commit abc1f34

Please sign in to comment.