[Discussion] UseSignalR and UseConnections are marked obsolete

[BrennanConroy]

The methods UseConnections and UseSignalR, and the classes ConnectionsRouteBuilder and HubRouteBuilder are being marked obsolete in 3.0. And will be removed in the next major release after that.

The preferred method for using SignalR starting in 3.0 is to use Endpoint Routing. See example below.

Old code:

app.UseSignalR(routes =>
{
    routes.MapHub<SomeHub>("/path");
});

New code:

app.UseEndpoints(endpoints =>
{
    endpoints.MapHub<SomeHub>("/path");
});

This is the discussion issue for aspnet/Announcements#362.

[VictorioBerra]

I haven't looked at the code yet, sorry if this is a dumb question. So UseEndpoints is a core thing (in a non-SigR namespace) and MapHub is a SignalR extension method for creating a new endpoint and mapping a hub to it?

[Kahbazi]

@VictorioBerra yes, there's also MapController extension method for mvc

[idrivediesel2006]

What is you're not using MVC, instead you're using Web API... What's the implementation for SignalR that is replacing the obsolete UseSignalR() method?

[davidfowl]

What is you're not using MVC, instead you're using Web API... What's the implementation for SignalR that is replacing the obsolete UseSignalR() method?

The code above is the same.

PS: MVC is the same thing as Web API in ASP.NET Core. It's a single framework.

[ghost]

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!