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.

Lots of errors when opening aspnet/SignalR

See original GitHub issue

I’m running on OSX.

I didn’t want to open an uber issue but it seems like there are multiple things happening here. The repro steps are to clone https://github.com/aspnet/SignalR and run build.sh. After the build finishes, open vs code at the root (code .).

I get warnings telling me there are unresolved dependencies even though restore ran.
I get 100s of errors talking about ambiguous references. It seems as though the sample projects don’t see the src projects within the same solution so packages are being resolved…

I’ll try to pick it apart into specific issues but I was caught by surprise because I thought things would just work.

Issue Analytics

State:
Created 7 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

DustinCampbellcommented, Apr 6, 2017

Nah, it wasn’t about SDKs. Project references were getting added twice due to some code that got lost in a refactoring a few months ago: https://github.com/OmniSharp/omnisharp-roslyn/commit/ef4b3838d39666ed5ca9780ea133bfdc08ff5844.

I’ve got a fix that should make SignalR work nicely for you.

0reactions

DustinCampbellcommented, Apr 6, 2017

If you don’t want to wait for a C# for VS Code update (which’ll be a little while yet), you can build the latest omnisharp-roslyn dev branch and set the following settings in VS Code:

"omnisharp.path" : “<path-to-the-net46-OmniSharp.exe>”
"omnisharp.useMono" : true

Build instructions are here