locked
SignalR Core for .NET 4.6.1 RRS feed

  • Question

  • User-2068832071 posted

    As said in the SignalR differences documentation (link) we can use SignalR Core on .NET 4.6.1 and latter...

    So I know the code for the startup and configuration for both cases:

    SignalR Core:

    ConfigureServices

    //Add SignalR service

    services.AddSignalR();

    Startup

    app.UseSignalR(routes =>{routes.MapHub<NotificationsHub>("/notification");});

    SignalR:

    Startup

    app.Map("/signalr", map =>{app.UseCors(CorsOptions.AllowAll);

    var hubConfiguration = new HubConfiguration { };

    hubConfiguration.EnableDetailedErrors = true;

    map.RunSignalR(hubConfiguration);});

    Also I know hot to do both client implementations (Angular).

    And my question is, what I need to do in the .NET 4.6.1 startup to map my SignalR hub and etc...? How I map signalR core on .NET FW project?

    I can't find any documentation about this particular case.

    Tuesday, October 8, 2019 9:43 AM

Answers

  • User61956409 posted

    Hi Kyrylo,

    Kyrylo Yavorenko

    what I need to do in the .NET 4.6.1 startup to map my SignalR hub and etc...? How I map signalR core on .NET FW project?

    In comparison table,  you can find the Server App Type of ASP.NET Core SignalR should be a ASP.NET Core application/project.

    The support server platforms include .NET Framework 4.6.1 or later, which means that it supports targeting framework to .NET Framework 4.6.1 or later then compile and run the application on supported platform.

    With Regards,

    Fei Han

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 9, 2019 2:48 AM