UPDATE - February 2017 This article describes the latest development of websocket-manager and how to use it in your application. While the general aspects provided in this article about creating a websockets middleware for Asp .Net Core are still valid, the specific information about the websocket-manager project have changed, since I updated a lot of parts. The version of the project described in this article can still be found in the blog-article branch on GitHub.
Introduction In this article, we will take the simplest ASP.NET Core application, run it with Docker locally, then create Continuous Integration and Continuous Deployment flows using a GitHub repository, Docker Cloud and an Azure virtual machine that will act as a node for Docker Cloud. If you don’t want to create an ASP.NET Core application but are interested in the CI/CD workflow, or if you already have a GitHub repository with a complete application with a Dockerfile, you might want to skip to the part we start creating the CI/CD workflow.
Introduction In this article we will take a look at how to integrate ASP.NET Core MVC with SignalR Core (at the moment of writing this article, the latest version of SignalR is 0.2.0-alpha1-22107) and how to use the SignalR context outside hubs (and solve the current issues with the custom resolvers that will be detailed later) to update clients. This article assumes a basic understanding of ASP.NET Core MVC and will not try to explain all concepts here.
Introduction ASP.NET SignalR is a library for ASP.NET developers that simplifies the process of adding real-time web functionality to applications. Real-time web functionality is the ability to have server code push content to connected clients instantly as it becomes available, rather than having the server wait for a client to request new data. The 1.0.0 version of ASP.NET Core didn’t include a version of SignalR, so the team plans to release SignalR in the 1.