Aspnetcore: Using AddAzureSignalR with Razor Conponents 3.0.0 preview 3

[ADefWebserver]

Describe the bug

Click events don't work

To Reproduce

Steps to reproduce the behavior:

1. Create new Razor Components project
   2, Add Microsoft.Azure.SignalR NuGet package
2. In startup.cs, change

services.AddRazorComponents()

to:

            services.AddRazorComponents()
                .AddSignalRCore()
                .AddAzureSignalR(
                "{{ Azure SignaleR connection string}}");

1. In startup.cs, in the "configure" method, add:

            app.UseAzureSignalR(route =>
            {
                route.MapHub<ComponentHub>(ComponentHub.DefaultPath);
            });

1. Run the application
2. The Fetch Data page will work, but clicking on the Counter, on the Counter page will not

Expected behavior

Clicking on the counter button will work

Additional context

When looking in Azure, there is traffic when the Fetch Data page is viewed

[davidfowl]

Yes this is being worked on for preview4. It's currently broken in preview3.

[asterinex]

Yes this is being worked on for preview4. It's currently broken in preview3.

Is there a temporary fix or workaround ?

[mkArtakMSFT]

@davidfowl, @anurse is there a separate issue you track the fix with? Should this one be duped?

[mkArtakMSFT]

This is probably caused by https://github.com/aspnet/AspNetCore/issues/8679

[anurse]

I don't think this is the same issue as #8679. Azure SignalR has a very different connection pattern.

[anurse]

@mkArtakMSFT We need someone from Razor Components to drive an investigation here, since we need client-side logs from SignalR. Can you look in to that?

[davidfowl]

This is already being worked on you can assign it to me

[anurse]

[davidfowl]

https://github.com/davidfowl/AzureSignalRLightupPrototype

[davidfowl]

The work here is mostly done on the SignalR side of things. The Azure SignalR SDK changes will be going in soon. It'll require some code changes as a result though.

[davidfowl]

@anurse moving this back into preview4 as we can't ship another preview that doesn't work with the service.

[anurse]

@davidfowl sync up with me on this ASAP then. This is super vague and I need to know what we actually need to get done here in order to actually be able to deliver it :).

[davidfowl]

The work is done on outside and is being integrated into the SDK, I still want to track it here though

[anurse]

Ok. Still want to sync, but that helps me understand the context and timing. Is there a doc or spec describing the change? Mostly, I'm just trying to figure out what the work is since that doesn't appear to have been described here, and if you want to use this to track that work it would certainly be nice to know what it is that actually needs to be done (even if you're just doing it) ;)

[BrennanConroy]

https://github.com/Azure/azure-signalr/pull/470 FYI

[davidfowl]

The runtime work here is done. I'll open bugs if there's remaining work to do in later previews.