Go to file
Mikael Mengistu 562b494229
New Idle Connection Benchmark Scenario (#2178)
2018-05-04 18:08:02 +00:00
.github issue template (#1701) 2018-03-23 12:29:09 -07:00
.vscode
benchmarkapps New Idle Connection Benchmark Scenario (#2178) 2018-05-04 18:08:02 +00:00
benchmarks/Microsoft.AspNetCore.SignalR.Microbenchmarks Add HubConnection receive benchmark (#2164) 2018-04-30 16:52:01 -07:00
build Update dependencies.props 2018-05-04 07:51:09 -07:00
clients Merge branch 'release/2.1' into dev 2018-05-04 09:06:45 -07:00
docs NPM troubleshooting documentation (#1529) 2018-03-06 10:41:51 +13:00
samples Merge pull request #2122 from aspnet/release/2.1 2018-04-20 16:22:16 -07:00
specs Added support for negotiate response to redirect the client to another SignalR endpoint (#2070) 2018-04-18 14:22:45 -07:00
src Merge pull request #2198 from aspnet/release/2.1 2018-05-03 19:10:42 -07:00
test Merge pull request #2198 from aspnet/release/2.1 2018-05-03 19:10:42 -07:00
.appveyor.yml Enable dotnet-build bot 2018-03-19 12:31:55 -07:00
.gitattributes Update .gitattributes to workaround npm changing line endings (#1610) 2018-03-15 19:41:57 -07:00
.gitignore Move Cpp Client to main repo (#1703) 2018-03-29 14:58:54 -07:00
.travis.yml Enable dotnet-build bot 2018-03-19 12:31:55 -07:00
CONTRIBUTING.md
Directory.Build.props Remove the custom C# compiler now that we're using the 2.2 SDK (#1168) 2017-11-30 08:42:53 -08:00
Directory.Build.targets Set NETStandardImplicitPackageVersion via dependencies.props 2018-04-19 16:45:04 -07:00
LICENSE.txt
NuGet.config Use MSBuild to set NuGet feeds instead of NuGet.config 2017-11-20 12:18:39 -08:00
NuGetPackageVerifier.json
README.md Add Gitter badge (#2174) 2018-04-30 23:22:46 -07:00
SignalR.sln Removing the chat sample (#2113) 2018-04-20 09:20:06 -07:00
THIRD-PARTY-NOTICES Move Cpp Client to main repo (#1703) 2018-03-29 14:58:54 -07:00
build.cmd Update bootstrappers 2017-10-09 12:43:40 -07:00
build.sh Update bootstrappers 2017-10-09 12:43:40 -07:00
korebuild-lock.txt Update dependencies.props 2018-05-04 07:51:09 -07:00
korebuild.json underp the merge 2018-04-18 09:13:13 -07:00
run.cmd Update bootstrappers 2017-10-09 12:43:40 -07:00
run.ps1 Enable dotnet-build bot 2018-03-19 12:31:55 -07:00
run.sh Enable dotnet-build bot 2018-03-19 12:31:55 -07:00
version.props Bump version to 1.0.0-rtm 2018-04-30 14:51:56 -07:00

README.md

ASP.NET Core SignalR

Join the chat at https://gitter.im/aspnet/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 SignalR

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.

TypeScript Version

If you are encountering TypeScript definition issues with SignalR, please ensure you are using the latest version of TypeScript to compile your application. If the issue occurs in the latest TypeScript, please let us know.

When in doubt, check the version of TypeScript referenced by our package.json file. That version is the minimum TypeScript version expected to work with SignalR.

Packages

You can install the latest released JavaScript client from npm with the following command:

npm install @aspnet/signalr

The @aspnet/signalr package (and it's dependencies) require NPM 5.6.0 or higher.

NOTE: Previous previews of the SignalR client library for JavaScript were named @aspnet/signalr-client. This has been deprecated as of Preview 1.

IMPORTANT: When using preview builds, you should always ensure you are using the same version of both the JavaScript client and the Server. The version numbers should align as they are produced in the same build process.

The CI build publishes the latest dev version of the JavaScript client to our dev npm registry as @aspnet/signalr. You can install the module as follows:

  • Create an .npmrc file with the following line: @aspnet:registry=https://dotnet.myget.org/f/aspnetcore-dev/npm/
  • Run: npm install @aspnet/signalr

Alternatively, if you don't want to create the .npmrc file run the following commands:

npm install @aspnet/signalr --registry https://dotnet.myget.org/f/aspnetcore-dev/npm/

We also have a MsgPack protocol library which is installed via:

 npm install @aspnet/signalr-protocol-msgpack

Deploying

Once you've installed the NPM modules, they will be located in the node_modules/@aspnet/signalr and node_modules/@aspnet/signalr-protocol-msgpack folders. If you are building a NodeJS application or using an ECMAScript module loader/bundler (such as webpack), you can load them directly. If you are building a browser application without using a module bundler, you can find UMD-compatible bundles in the dist/browser folder; minified versions are provided as well. Simply copy these to your project as appropriate and use a build task to keep them up-to-date.

Building from source

To run a complete build on command line only, execute build.cmd or build.sh without arguments.

If this is your first time building SignalR please see the Getting Started for more information about project dependencies and other build-related information specific to SignalR.

See developer documentation for general information on building and contributing to this and other aspnet repositories.