-
Notifications
You must be signed in to change notification settings - Fork 677
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
[MacOS] Cannot start OmniSharp because Mono version >=6.4.0 is required." after upgrade to latest vscode version(1.54.1) #4428
Comments
this suggests that msbuild is missing or out of date in the mono installation. did you install using the official package from https://www.mono-project.com/download/stable? e.g. homebrew mono is known to be missing msbuild |
@filipw hi, I'm re-install from the official package as you said. |
just test
|
what does |
I've been having issues that sound similar to this, posted here: https://stackoverflow.com/questions/66507869/cannot-start-omnisharp-because-mono-version-6-4-0-is-required |
if you echo $PATH from inside VS Code (e.g. VS Code terminal) does it have
in it? It is a bit unfortunate that the extensions does this check - because the OmniSharp server will also do it, and then print more info if something is missing. We have seen problems like these happen with brew installations in the past due to missing MSBuild. You should try to get rid of the brew installation, and only use the official installer https://www.mono-project.com/download/stable. Also make sure the above path is in the PATH, instead of |
Gotcha. I did
Yet the OmniSharp logs still only say |
I have the same issue starting recently. My copy of mono is installed by Visual Studio for Mac. |
I'm running into the same problem. I've set both my monoPath to the current mono build (6.12.0.10) and useGlobalMono to always. When running mono in te terminal, everything seems to work fine. But the |
@filipw only one word print in
Yes. with |
I'm upgrade macOS to latest 11.2.2 and download Visual Studio for Mac temporarily (which swallow 800+M memory :-( . Hopes VS code finally fixed. |
I downgraded to Visual Studio Code 1.52.1 at https://code.visualstudio.com/updates/v1_52 and turned off automatic updates in VS Code and OmniSharp is now working without any exceptions. Seems likely that the root cause lies with |
@LoranceChen Sorry you are having issues getting the C# extension configured. It is not normally necessary to set the "omnisharp.monoPath" setting if mono is already on your PATH. If you do need to set it, then it should match your |
I think people have this set was to workaround issues. Previously on an older Omnisharp + VS Code combination, I had the same mono not found issue, and I had to do this so that Omnisharp could pick up the Mono SDK path since the setting kept coming back as empty string in global settings.json after several attempt to remove it. Not sure if it was just a coincidence, but the issue did go away. |
@JoeRobich thanks! I changed monoPath as |
My Unity3D project c# do not work after auto upgrade vscode 1.54.1 version today.
I have re-install latest mono(6.12) and dotnet core(3.1.4) but not work still. for detail:
other settings:
thanks.
The text was updated successfully, but these errors were encountered: