Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

Azure SignalR Service

Sign in to queue

The Discussion

  • User profile image
    Electric Fan

    i'm a fan of John Lam! :-)

  • User profile image
    alexmarshal​l132

    In these types of videos, I'd really like to see references to contacts at Microsoft that can help out with more advanced scenarios, e.g. pushing to SignalR as a Service from a Service Fabric service, i.e. something that's NOT a customer facing ASP.NET application.

  • User profile image
    Varghese Cherian

    Can i use AzureSignalR service with a regular mvc application that is build on .net framework v.6?In the github it shows only .net core

  • User profile image
    Varghese Cherian

    .net framework 4.6

  • User profile image
    robcaron

    @alexmarshall132: From the team: "Yes, the use case scenario doesn't have to be customer-facing. The Azure SignalR Service implements REST APIs, so any backend service/application can post real-time messages to the service, then the service sends to receiving connections, either web browsers, or a backend ASP.NET apps. The SignalR client-side SDK currently provides JS (mainly for web) and C# (for .NET app). For other services or other languages, REST API or Azure Function binding can be used."

  • User profile image
    robcaron

    @Varghese Cherian: From the team: "For .NET back compatibility, there are 4 combinations for client-side SignalR applications to work with Azure SignalR Service (ASRS), which is ASP.NET core based. .NET web app + .NET SignalR SDK, requires a new version of .NET SDK to work with ASRS. The SDK is being worked right now with a high priority; .NET web app + .NET core SignalR SDK, as long as the SignalR related code can be separated from .NET based web app, this works right now; .NET core web app + .NET SignalR SDK, this won't be supported in near future; .NET core web app + .NET core SignalR SDK, this is recommended and is supported in production. For any customer that cannot migrate the web app to .NET core, the immediate solution is to separate the SignalR related logic and implement in .NET core, using .NET core SignalR SDK. If the user wants to wait a while, then there will be the new version of .NET SignalR SDK, to make it happen, but not 100% of APIs will be covered."

  • User profile image
    Paulsvx

    This looks great. Most of our enterprise clients that use our SaaS product will end up blocking cross-domain calls from the browser. Will it be possible to setup a custom DNS for the Azure SignalR service? That would be super handy. 

Add Your 2 Cents