- Getting started with SignalR using ASP.NET Core and Angular
- SignalR Group messages with ngrx and Angular
- Using EF Core and SQLite to persist SignalR Group messages in ASP.NET Core
- Securing an Angular SignalR client using JWT tokens with ASP.NET Core and IdentityServer4
- Implementing custom policies in ASP.NET Core using the HttpContext
- Sending Direct Messages using SignalR with ASP.NET core and Angular
- Using Message Pack with ASP.NET Core SignalR
2018-05-04: Updated to Angular 6
2018-04-22: Updating nuget packages and npm packages, @aspnet/signalr 1.0.0-preview2-final, Microsoft.AspNetCore.SignalR 1.0.0-preview2-final
2018-03-19: Added example for Message Pack
2018-03-14: Updated signalr Microsoft.AspNetCore.SignalR 1.0.0-preview1-final, Angular 5.2.8, @aspnet/signalr 1.0.0-preview1-update1
2017-10-15: Updated signalr 1.0.0-alpha2-final
https://github.com/aspnet/SignalR#readme
https://www.npmjs.com/package/@aspnet/signalr https://www.npmjs.com/package/msgpack5
https://dotnet.myget.org/F/aspnetcore-ci-dev/api/v3/index.json
https://dotnet.myget.org/F/aspnetcore-ci-dev/npm/ https://dotnet.myget.org/feed/aspnetcore-ci-dev/package/npm/@aspnet/signalr-client
"@aspnet/signalr": "^1.0.0-preview2-final",
"msgpack5": "4.0.2",
The new uglifyjs-webpack-plugin is required.
in the package.json add:
"uglifyjs-webpack-plugin": "1.0.0-beta.2",
add the UglifyJSPlugin webpack plugin (S is capital), in the webpack production build file
const UglifyJSPlugin = require('uglifyjs-webpack-plugin');
Update the webpack production build
new UglifyJSPlugin({
parallel: {
cache: true,
workers: 2
}
}),