-
Notifications
You must be signed in to change notification settings - Fork 64
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
OmniSharp: Error talking to localhost #250
Comments
read the README, you need |
@tim241 Installing msbuild did not resolve the issue, either. |
is it included in your PATH then?
also, what msbuild version do you have?
It all states this clearly in the README
…On 20.10 07:27, zshep427 wrote:
@tim241 Installing msbuild did not resolve the issue, either.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#250 (comment)
|
I added this filepath to PATH: C:\Program Files (x86)\MSBuild\14.0\Bin Is that correct? It's 2015, downloaded from here: https://www.microsoft.com/en-us/download/details.aspx?id=48159 Thanks for your help! |
seems correct, does it work now or does it still not work? |
Nope, still doesn't work. Still receiving the same "Error talking to localhost" when I launch Sublime and it attempts to start the server. |
Can you try to execute omnisharp.cmd manually in cmd to see what it says then? |
Says that omnisharp.cmd is not recognized as a command. Will I not have that if I installed OmniSharp via Package Control? |
|
@kufii is the correct |
Yes 2015 |
@kufii please show me the output of |
|
@tim241
and after tryng to execute it, the same output of @kufii
My msbuild version:
|
Does omnisharp-sublime 1.9.9 fix it? (I updated omnisharp-roslyn and the msbuild detector seems to be improved) |
@tim241 nope, upgraded and the bug remained, then removed omnisharp and msbuild and started all over again and still the
|
Today Package Control told me that it failed when upgrading Omnisharp and suggested restarted Sublime. But I'm now getting It was all working fine last week. |
Alright, for 2.0.0 I've reverted the previous commit (the omnisharp-roslyn) update I'll take a closer look now. EDIT: I'm sorry for causing any inconveniences, I hope I'll get this fixed ASAP |
@tim241 2.0.0 is working now. Thanks |
I'm seeing this issue on 2.0.0. This is a fresh install of omniSharp-sublime through Sublime package control. |
I'm also had this problem on 2.0.0. About fresh install, by instruction. |
On linux I had to install the dot net core sdk https://dotnet.microsoft.com/download/linux-package-manager/debian9/sdk-2.2.104 |
Hey @tim241 thanks for all the great work on this project. I'm getting the
error running v2.0.0 on OSX as well. Is this something that might be resolved temporarily by running an earlier version of omnisharp-sublime? |
I was able to get things running by downloading the latest omnisharp-rosyln release: https://github.com/OmniSharp/omnisharp-roslyn/releases and manually starting the server with the |
@yohanmishkin are you sure the code is in focus? that error generally only pops up once you have the warning/log window in focus |
Thanks, @tim241. I thought I had the code in focus, but things appear kosher now. So thanks for checking in! |
I'm also getting the
I have installed the net core sdk, and tried manually starting the server |
Any solution for that? I've done everything possible and I haven't solved anything :/ |
Fascinatingly, I have been trying to make this work in Windows 10 for hours then gave up. In my Linux laptop, it just worked out of the box. Well to be fair, I already access to Mono and MSBuild in my Linux, so that's most likely the reason why. Sublime Text and Omnisharp must have access to both Mono and MSBuild. I tried using |
Same Error! Same output as @kufii when execute |
@Rosalie241, @0xPlaydevil, Hi! Just out of interest: are you using any specific Visual Studio version [which pretty much implies specific tools version]? Both suggestions don't apear to fix the issue:
Building from source results with the same hurdles. Probably, this plugin strictly requires older tools version (Microsoft Build Tools 2015)? I've even installed Also, it's been around 2 years since the last commit. Is everything's fine, or is it VSCode + I remember using Sublime with OmniSharp, kek, almost 8 years ago or so - everything was fine then. I'll give the setup a go some time later, probably. |
Platform
Type
Checklist
Versions
output of
mono --version
:output of
msbuild /version
:Details
This might be less of a bug and more of an issue with my setup. I was using the setup detailed here https://www.youtube.com/watch?v=z7na1MuMDRg and it was working up until about a week ago. I tried several different solutions I found for recent issues I found on the internet (reinstalling from scratch, doubling the time for connection timeout, updating Mono to latest, etc and it keeps failing). I was hoping my problem might just be something obvious I'm not seeing. Every time I launch ST I get the error:
"OmniSharp: Error talking to http://localhost:xxxxx/checkreadystatus"
Thanks in advance for your help! Hopefully it's something simple.
How-To
How do I reproduce this issue?
The text was updated successfully, but these errors were encountered: