Go to file
moozzyk 82f99a1424 Work around for a Firefox bug
Firefox won't fire EventSource open event until it receives some data. The workaround is to send an empty comment when starting ServerSentEvent transport.

Fixes: #352
2017-04-27 10:34:47 -07:00
build Branching for 2.0.0-preview1 2017-04-25 22:05:44 -07:00
client-ts Preserving user's queryString 2017-04-27 09:50:14 -07:00
samples Work around for a Firefox bug 2017-04-27 10:34:47 -07:00
specs
src Work around for a Firefox bug 2017-04-27 10:34:47 -07:00
test Work around for a Firefox bug 2017-04-27 10:34:47 -07:00
typings
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE.txt
NuGet.config Branching for 2.0.0-preview1 2017-04-25 22:05:44 -07:00
NuGetPackageVerifier.json
README.md
SignalR.sln
appveyor.yml
build.cmd
build.ps1 Branching for 2.0.0-preview1 2017-04-25 22:05:44 -07:00
build.sh Branching for 2.0.0-preview1 2017-04-25 22:05:44 -07:00
version.props Updating package version to preview2 2017-04-26 07:13:40 -07:00

README.md

ASP.NET Core SignalR

AppVeyor: AppVeyor

Travis: Travis

ASP.NET Core SignalR is a new library for ASP.NET Core developers that makes it incredibly simple to add real-time web functionality to your applications. What is "real-time web" functionality? It's the ability to have your server-side code push content to the connected clients as it happens, in real-time.

You can watch an introductory presentation here - Introducing ASP.NET Core Sockets.

This project is part of ASP.NET Core. You can find samples, documentation and getting started instructions for ASP.NET Core at the Home repo.

Note To build the project locally at this time you will need the TypeScript Compiler on your path.

The JavaScript client is being published to our dev npm registry. The module contains a browserfied version of the client. You can install the module using the following command:

npm install signalr-client --registry https://dotnet.myget.org/f/aspnetcore-ci-dev/npm/