[Question] - Reason for this library?

I am looking to use signalr client in my blazor (client side) app. My first thought was to add the official signalr.client nuget package:

<PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="3.0.0-preview6.19307.2" />

Then I stumbled accross this project which wraps the typescript version - i’m assuming there must be a reason why the Microsoft.AspNetCore.SignalR.Client package I have referenced above won’t work in blazor client applications and why this project exists? Are you able to clarify what the reason is as that will help me decide what to do!

Cheers

[galvesribeiro]

By the way thanks for this library it is working well in my application (preview 6)

No problem. And glad to know it is working!

I’m using HttpClient fine from a client side blazor app - it’s constructed using the web assembly http handler which marshalls requests through javascript fetch api

Yeah I think my answer was not that accurate… SignalR client is based on the new transport abstractions just like the server. One can theoretically implement it by wrapping the correct APIs on JS/WASM. The current implementation don’t work now.

This package was also created before that abstrations were in place. So if you find the correct way to implement it, please suggest it in an issue and perhaps if you feel in the mood, feel free to make a PR.

I always love to get rid of JS 😄

Thanks!

[vavjeeva]

I’m using HttpClient fine from a client side blazor app - it’s constructed using the web assembly http handler which marshalls requests through javascript fetch api. So if HttpClient works in Blazor I’m assuming the problem must be that signalr client doesnt allow you to pass your own http client or something?

signalR client on client side blazor is not supported yet due to websocket support in runtime which is not enabled yet. You can see the response from dan in the below link.

https://github.com/aspnet/AspNetCore/issues/9825#issuecomment-488028164