More guidance around migrating from SignalR (.NET Framework) to Azure SignalR

[samaea]

Hi all,

Those migrating over from SignalR Asp.net (.NET Framework) will typically have configured a custom SignalR endpoint path (instead of the default /signalr path). As such, it would be useful to include an example of doing this to make their clients compatible without further code changes.

An example below shows this:-

        public void Configuration(IAppBuilder app)
        {
            // Maps the SignalR path endpoint to /monitorhub instead of the default /signalr

            app.MapAzureSignalR("/monitorhub", this.GetType().FullName, new HubConfiguration());

        }

Another item of feedback which would be useful to incorporate is what frontend changes need to happen in order to get it working with Azure SignalR. In my scenario, I had to update the jQuery Signal library from 2.1.0 to 2.4.1, otherwise the connection would fail (even though this works when SignalR is hosted locally).

Thanks, Sam

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: fc0d54cb-58bd-14fc-6fca-1691f3b151a2
• Version Independent ID: 6b65a485-51dc-4f09-f512-67cb9389f3a3
• Content: Develop with ASP.NET - Azure SignalR Service
• Content Source: articles/azure-signalr/signalr-quickstart-dotnet.md
• Service: signalr
• GitHub Login: @vicancy
• Microsoft Alias: lianwei

[AjayKumar-MSFT]

@samaea, Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.