Go to file
David Fowler 8da2dddd49 Fix issue where multiple calls to dispose don't wait properly (#360)
* Fix issue where multiple calls to dispose don't wait properly
- DisposeAsync returned immediately to anyone but the first caller.
This means that it was possible to end the request before properly
waiting on the transport task which means writing after dispose was possible.
- Added a test
2017-04-03 15:25:45 -07:00
build Updating to 2.0.0 Internal.AspNetCore.Sdk 2017-03-29 11:30:37 -07:00
client-ts * Fixing a racey test 2017-03-31 13:54:46 -07:00
samples
specs
src Fix issue where multiple calls to dispose don't wait properly (#360) 2017-04-03 15:25:45 -07:00
test Fix issue where multiple calls to dispose don't wait properly (#360) 2017-04-03 15:25:45 -07:00
typings
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md
SignalR.sln Using common XUnitLoggerProvider 2017-03-27 16:19:40 -07:00
appveyor.yml
build.cmd
build.ps1
build.sh
version.props

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/