Go to file
dotnet-maestro-bot c206ea612a [automated] Merge branch 'release/2.2' => 'master' (#3278)
I detected changes in the release/2.2 branch which have not been merged yet to master. I'm a robot and am configured to help you automatically keep master up to date, so I've opened this PR.

This PR merges commits made on release/2.2 by the following committers:

* @anurse

## Instructions for merging

This PR will not be auto-merged. When pull request checks pass, please complete this PR by creating a merge commit, *not* a squash or rebase commit.

<img alt="merge button instructions" src="https://i.imgur.com/GepcNJV.png" width="300" />

You can also do this on command line:

```
git checkout -b merge/release/2.2-to-master master
git pull https://github.com/dotnet-maestro-bot/SignalR merge/release/2.2-to-master
git checkout master
git merge --no-ff merge/release/2.2-to-master
git push origin master
```

## Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this [using GitHub][resolve-github] or using the [command line][resolve-cli].

[resolve-github]: https://help.github.com/articles/resolving-a-merge-conflict-on-github/
[resolve-cli]: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

## Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/2.2-to-master'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

```
git checkout -b merge/release/2.2-to-master master
git pull https://github.com/dotnet-maestro-bot/SignalR merge/release/2.2-to-master
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/SignalR merge/release/2.2-to-master
```

Please contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.
2018-11-07 15:27:19 -08:00
.github
.vscode [Java] Make public API look like RxJava (#3103) 2018-10-10 08:50:41 -07:00
.vsts-pipelines/builds Merge pull request #3163 from dotnet-maestro-bot/merge/release/2.2-to-master 2018-10-19 14:58:53 -07:00
benchmarkapps Remove SignalR.Redis package (#3241) 2018-10-31 15:16:44 -07:00
benchmarks/Microsoft.AspNetCore.SignalR.Microbenchmarks Merge branch 'release/2.2' 2018-10-11 10:25:47 -07:00
build Merge pull request #3249 from dotnet-maestro-bot/merge/release/2.2-to-master 2018-11-01 15:18:27 -07:00
clients Merge branch 'release/2.2' 2018-11-06 14:52:50 -08:00
docs Refine documentation formatting (#3080) 2018-10-07 17:27:46 -07:00
samples Remove SignalR.Redis package (#3241) 2018-10-31 15:16:44 -07:00
specs Refine documentation formatting (#3080) 2018-10-07 17:27:46 -07:00
src Wrap log in enabled check 2018-11-06 09:24:34 -08:00
test Merge branch 'release/2.2' 2018-11-07 08:52:13 -08:00
.gitattributes
.gitignore
.gitmodules
.travis.yml
CONTRIBUTING.md
Directory.Build.props Include .jar files in microbuild code signing 2018-09-28 11:22:16 -07:00
Directory.Build.targets
LICENSE.txt Update LICENSE.txt 2018-09-27 15:23:23 -07:00
NuGet.config
NuGetPackageVerifier.json
README.md [automated] Merge branch 'release/2.2' => 'master' (#3278) 2018-11-07 15:27:19 -08:00
SignalR.sln Remove SignalR.Redis package (#3241) 2018-10-31 15:16:44 -07:00
THIRD-PARTY-NOTICES Add gradle to 3pn (#2798) 2018-08-13 14:56:42 -07:00
build.cmd
build.sh
korebuild-lock.txt Update dependencies.props 2018-10-11 12:26:21 -07:00
korebuild.json
run.cmd
run.ps1 automated: bulk infrastructure updates. Update bootstrapper scripts and remove unnecessary signing properties 2018-09-28 17:16:37 -07:00
run.sh automated: bulk infrastructure updates. Update bootstrapper scripts and remove unnecessary signing properties 2018-09-28 17:16:37 -07:00
version.props Merge branch 'release/2.2' 2018-10-11 10:25:47 -07:00

README.md

ASP.NET Core SignalR

IMPORTANT: This repository hosts code and project management for ASP.NET Core SignalR, for use in ASP.NET Core applications using Microsoft.AspNetCore.App. If you are looking for information on ASP.NET SignalR (used in .NET Framework applications using System.Web and/or Katana), see the https://github.com/SignalR/SignalR repository.

Build Status NuGet version npm version Maven Version

Join the chat at https://gitter.im/aspnet/SignalR

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 - ASP.NET Core SignalR: Build 2018

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.

Documentation

Documentation for ASP.NET Core SignalR can be found in the Real-time Apps section of the ASP.NET Core Documentation site.

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.