Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Question] - Reason for this library?

See original GitHub issue

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!


Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

galvesribeirocommented, Jul 2, 2019

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 😄


vavjeevacommented, Jul 3, 2019

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

33 Interview Questions for a Library Assistant
Library assistant questions about experience and background · Do you have research experience? · Do you have strong communication skills ? · Do...
Read more >
Why do you want to work for this Library?
The interviewer will want to hear why you are interested in being a librarian and why you want to work at that particular...
Read more >
Top 13 Library Assistant Interview Questions & Answers
Why do you want to work as a library assistant? How would you define excellent customer service in a library? This is a...
Read more >
The 50 Most Asked Library Assistant Interview Questions ...
1. What do you think are the essential characteristics of a library assistant? · Answer: · 2. Tell me about your passion for...
Read more >
Sample Librarian Interview Questions and Answers
What Is Your Vision for the Future of Libraries? Question #1: Which of Your Skills Will Help You Succeed as a Librarian? Your...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found