SignalR-FSharp-Example
Example of SignalR 1.1.1 with F-Sharp (and Silverlight 5 or Javascript): - SignalR is a library (for web-based Publish/Subscribe -pattern) on top of WebSockets, which is HTML5 API that enables bi-directional communication between the browser and server. SignalR will fallback to other techniques and technologies when WebSockets are not available. http://signalr.net/ - F-Sharp (F#) is multiparadigm (functional-first) programming language mainly for .NET environment. http://fsharp.org/ - This sample uses Reactive Extensions 2.1 to communicate with SignalR, on both client and server side. Reactive Extensions is a library to compose asynchronous and event-based programs using observable collections and LINQ-style query operators. http://msdn.microsoft.com/en-us/data/gg577609.aspx - For server side: This could work purely from F# as Owin (http://owin.org/) console application but now Owin-code is in comments and F#-server-side is called from an empty ASP.NET C# Web Application. (Still you can start OWin from F# Interactive...) - For client side: Silverlight 5.0 application using F#-library and Silverlight 5.0 XAML/C# application to show the user interface. http://www.silverlight.net There is also jQuery/JavaScript test page, if you don't want to use Silverlight. - This proof of concept/sample/tutorial/demo is developed with Visual Studio 2012. References are resolved via NuGet. F# compiler won't auto-restore packages on compile. So go first to Tools -> Library Package Manager -> NuGet and press "Restore" to restore all the references, and then rebuild. - SignalR supports two kinds of connections: Hub and PersistentConnection Both are working with Silverlight and JavaScript.
Install
dotnet add package SignalR-FSharp-Example --version 1.0.2
Install-Package SignalR-FSharp-Example -Version 1.0.2
<PackageReference Include="SignalR-FSharp-Example" Version="1.0.2" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.