-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unity 2020.3.25 projects fails to find project files #12
Comments
I think this is because we use the bundled |
Here's the full output from VSCode. It looks like it may be using mono 6.12.0 from a system framework outside of VSCode. What version is ST using?
|
Has anyone been able to make any progress in this? I've tried reassingning "FrameworkPathOverride" to point to my 6.12 Mono install but apparently had no success, still the same issues. Has msbuild and mono in PATH but still a no. How can we point the bundled OmniSharp to correctly point to a globally installed Mono? In this issue: OmniSharp/omnisharp-roslyn#1948 Some Mac and Linux users were able to solve this by doing that. |
I have a version of LSP-OmniSharp that seems to be working with Unity on Mac. Part of that is specifying the mono binary location explicitly as a setting. Let me know if there's interest in getting this into the main repo. |
Should be fixed by PR #40, which makes transition to latest .NET 6+ based OmniSharp binaries. |
When I upgraded Unity my project files ceased to load in LSP-Omnisharp.
In VSCode the project still loads properly and this is probably due to the dated version of Omnisharp server being used. Suggestion is to upgrade to 1.38.0 like VSCode uses.
The text was updated successfully, but these errors were encountered: