question-mark
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.

Make OmniSharp "latest" more reliable

See original GitHub issue

I’m using the settings "omnisharp.path": "latest" and my VS Code can’t download the latest version and it might be related to the CDN that provides the download files. I’ve search a bit and found that this already happened a few times (#2681, #2738 & #2741).

Omnisharp Log:

Error occured in loading omnisharp from omnisharp.path
Could not start the server due to Error: 404

C# Log:

Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.32.11-beta.1...
Platform: win32, x86_64

Downloading package 'OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.11-beta.1' Failed to download from https://roslynomnisharp.blob.core.windows.net/releases/1.32.11-beta.1/omnisharp-win-x64.zip. Error code '404')
Failed at stage: downloadAndInstallPackages
404

The output from URL (https://roslynomnisharp.blob.core.windows.net/releases/1.32.11-beta.1/omnisharp-win-x64.zip)

BlobNotFoundThe specified blob does not exist.
RequestId:39f4cf1b-101e-005b-4a7c-b9e374000000
Time:2019-01-31T15:50:50.9362539Z

Issue Analytics

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

github_iconTop GitHub Comments

6reactions
Fubuchicommented, Mar 21, 2019

You guys can check for all available version here : https://roslynomnisharp.blob.core.windows.net/releases?restype=container&comp=list

The latest beta version available for windows is 1.32.12-beta.51 so set "omnisharp.path": "1.32.12-beta.51" do the trick and allow you to continue your work while waiting for the fix.

Credit to @divinebovine in #2741

1reaction
filipwcommented, Mar 20, 2019

I restarted the build, and the latest is available now - sorry for the trouble.

Read more comments on GitHub >

github_iconTop Results From Across the Web

The Real Ultimate Guide to Fixing OmniSharp in VS Code | Blog
For good measure, click on Regenerate project files, and save your project. It's recommended that, after adding new packages, you simply open ...
Read more >
vs code Problems with C# extension, Some projects have ...
The most common solution is to make sure Mono is installed on your machine (https://mono-project.com/download/) and that OmniSharp is started ...
Read more >
PSA for those writing C# in VSCode (all 10 of us): Omnisharp ...
Last time I tried using vscode for c#, it was just constantly analyzing the bin folder despite it being excluded. Just never seems...
Read more >
Microsoft's PowerShell Dev Team Helps Fix OmniSharp
In announcing an update to the PowerShell extension for Visual Studio Code, Microsoft's dev team revealed it helped fix the latest edition ...
Read more >
[Solved] Problems with OmniSharp and Visual Studio Code
After the update, OmniSharp fails to validate the Unity project files ... a new class, VS Comm 2015 doesn't (always?) make the connection ......
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 Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found