Skip to content
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

C# v1.24.2 omnisharp/OmniSharp.exe"': No such file or directory. #5140

Closed
spdrcd opened this issue Apr 1, 2022 · 9 comments · Fixed by #5141
Closed

C# v1.24.2 omnisharp/OmniSharp.exe"': No such file or directory. #5140

spdrcd opened this issue Apr 1, 2022 · 9 comments · Fixed by #5141

Comments

@spdrcd
Copy link

spdrcd commented Apr 1, 2022

Environment data

dotnet --info output:
VS Code version: 1.66.0
C# Extension version: 1.24.2

OmniSharp log

Starting OmniSharp server at 4/1/2022, 11:50:34 AM
Target: project location

OmniSharp server started with Mono 6.8.0.
Path: /Users/{{username}}/.vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-x64/.omnisharp/1.38.3-beta.31/omnisharp/OmniSharp.exe
PID: 1898

Cannot open assembly '"/Users/chiehchihchen/.vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-x64/.omnisharp/1.38.3-beta.31/omnisharp/OmniSharp.exe"': No such file or directory.
[ERROR] Error: OmniSharp server load timed out. Use the 'omnisharp.projectLoadTimeout' setting to override the default delay (one minute).

Steps to reproduce

update to v1.24.2 on mac, tries to run VScode C# on mac

Expected behavior

To be able to run, use intellisense properly without issue

Actual behavior

Cannot open assembly '"Users/{{username}}/.vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-x64/.omnisharp/1.38.3-beta.31/omnisharp/OmniSharp.exe"': No such file or directory.
[ERROR] Error: OmniSharp server load timed out. Use the 'omnisharp.projectLoadTimeout' setting to override the default delay (one minute).

@hansihe
Copy link

hansihe commented Apr 1, 2022

Having the same issue

@filipw
Copy link
Contributor

filipw commented Apr 1, 2022

According to the logs you are using prerelease of OmniSharp server - 1.38.3-beta.31. This means you opted into pulling the latest builds from master. Remove the setting "omnisharp.path":"latest" from your config and try again.

@dmackdev
Copy link

dmackdev commented Apr 1, 2022

I am having the same issue on mac, even with omnisharp 1.38.2 and ms-dotnettools.csharp 1.24.2 and "omnisharp.path":"latest not present in my .vscode/settings.json.

I have installed ms-dotnettools.csharp 1.24.1 and removed .vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-arm64 and this now works. Culprit seems to be latest version of this extension.

@verbess
Copy link

verbess commented Apr 1, 2022

According to the logs you are using prerelease of OmniSharp server - 1.38.3-beta.31. This means you opted into pulling the latest builds from master. Remove the setting "omnisharp.path":"latest" from your config and try again.

The same issue was encountered with C# Extension version - 1.24.2, OmniSharp server - 1.38.2.
But C# Extension version - 1.24.1, OmniSharp server - 1.38.1 works.

OmniSharp Log

OmniSharp server started with Mono 6.12.0.
Path: /Users/{{username}}/.vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-x64/.omnisharp/1.38.2/omnisharp/OmniSharp.exe
PID: 13348

Cannot open assembly '"/Users/{{username}}/.vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-x64/.omnisharp/1.38.2/omnisharp/OmniSharp.exe"': No such file or directory.

@filipw
Copy link
Contributor

filipw commented Apr 1, 2022

You are right, it's an unfortunate regression. Really sorry about that.

We have a fix in the making, in the meantime, if you are doing .NET Core development only, you can set "omnisharp.useModernNet": true which will opt you into .NET 6 build of OmniSharp which is anyway much more stable and more performant. This variant is not affected.

If you are doing .NET Framework development, you need to roll back to 1.24.1 until the fix is rolled out.

@Ping-Gao
Copy link

Ping-Gao commented Apr 1, 2022

I am having the same issue on mac, even with omnisharp 1.38.2 and ms-dotnettools.csharp 1.24.2 and "omnisharp.path":"latest not present in my .vscode/settings.json.

I have installed ms-dotnettools.csharp 1.24.1 and removed .vscode/extensions/ms-dotnettools.csharp-1.24.2-darwin-arm64 and this now works. Culprit seems to be latest version of this extension.

That worked for me, thx.

@spdrcd
Copy link
Author

spdrcd commented Apr 1, 2022

You are right, it's an unfortunate regression. Really sorry about that.

We have a fix in the making, in the meantime, if you are doing .NET Core development only, you can set "omnisharp.useModernNet": true which will opt you into .NET 6 build of OmniSharp which is anyway much more stable and more performant. This variant is not affected.

If you are doing .NET Framework development, you need to roll back to 1.24.1 until the fix is rolled out.

You are right, it's an unfortunate regression. Really sorry about that.

We have a fix in the making, in the meantime, if you are doing .NET Core development only, you can set "omnisharp.useModernNet": true which will opt you into .NET 6 build of OmniSharp which is anyway much more stable and more performant. This variant is not affected.

If you are doing .NET Framework development, you need to roll back to 1.24.1 until the fix is rolled out.

Thank you so much to letting me know about working on fixing this issue!!
I did rolled back and it works for now...

@nohwnd
Copy link
Member

nohwnd commented Apr 1, 2022

Fix is merged, thanks @filipw The packages for 1.24.3 are building.

@nohwnd nohwnd pinned this issue Apr 1, 2022
@spdrcd
Copy link
Author

spdrcd commented Apr 1, 2022

Fix is merged, thanks @filipw The packages for 1.24.3 are building.

@nohwnd Thank you all I see it is building right now. Hope to update once it is propagated to VScode extensions 😄

@nohwnd nohwnd unpinned this issue Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants