New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in signalr.exe ghp
#4128
Comments
The core error is coming from your server (the other messages are warnings). It looks like there's a dependency conflict with the version of JSON.NET you are using: Could you post which version of Newtonsoft.Json is in your |
Also if you could link to the tutorial you're following that would help, as we can see if we can reproduce the issue by following the same steps. |
It's from a PluralSight so you'll need a subscription there Christian explains how to install and run the signalr CLI somewhere in the second half of SignalR Clients --> Demo: jQuery Clients 1 I followed all the steps that lead up to this video except I used VS2017 with the newest web templates. |
I don't have access to my home computer right now but it was probably version 11. But definitely something newer than 6. |
Ok. SignalR depends on Newtonsoft.Json 6.0.0, which is where that version number is coming from. However, NuGet should have installed a binding redirect in to your |
That doesn't sound right. NuGet wouldn't automatically add binding redirects for the utils package because it doesn't declare that it depends on Newtonsoft.Json 6.
https://www.nuget.org/packages/Microsoft.AspNet.SignalR.Utils/ But even if I add binding redirects to my Web.config manually, I still wouldn't expect it to work. The |
It's the server that has the binding failure. The Utils package gives you the tool, but when running the tool it connects to your SignalR server in order to gather data about the Hubs in order to generate proxies. Can you post more information about your server project? That's where the error is occurring. |
Hmm but how does that work? I get the same error even when my site is down, and even when I leave off the Project files available here: https://github.com/StevenLiekens/ghpcrash Running the |
Well that's interesting. I'll have to take a look. It's possible I'm misreading the stack trace. |
Hrm, I'm not getting that error at all, I just get this:
Can you try on a different machine? I wonder if maybe you have something installed on the machine that's causing problems. |
Diffferent machine, same error... can you try on a different machine? |
I have updated SignalR from v2.2.2 to v2.3.0. The config file of "signalr.exe" ("signalr.exe.config") seems to be missing in the "Microsoft.AspNet.SignalR.Utils" NuGet package in v2.3.0. In v2.2.2 the config file is shipped with the NuGet package. The generation seems to work if "signalr.exe.config" from v2.2.2 is copied in the directory of "signalr.exe" from v2.3.0. |
Thanks @CGX106 , I'll take a look at this. Glad there's a temporary workaround for you |
This is the same issue as #4152 . Closing this issue so we only have one issue tracking the work :). |
I'm following a tutorial that teaches the usage of the CLI tool.
https://www.nuget.org/packages/Microsoft.AspNet.SignalR.Utils/
I don't know exactly what is going on but the tool doesn't work on my machine.
Expected behavior
It shouldn't crash?
Actual behavior
Steps to reproduce
I don't know, basically install the tool and try to run it.
..\packages\Microsoft.AspNet.SignalR.Utils.2.2.3\tools\signalr.exe ghp /url:http://localhost:60946/
The text was updated successfully, but these errors were encountered: