-
Notifications
You must be signed in to change notification settings - Fork 676
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 project w/ v1.5 of plugin non-functional (never leaves Running state) #934
Comments
Yep, seems to happen with a fresh Unity project without dotbunny/VSCode installed as well. |
Hmmm... it looks like you have mono installed at /usr/local/bin/mono. Is that right? |
Could you run |
Also, does the following directory exist on your system?
|
And (last question), how did you install Mono on machine. Did you install it from an official Mono release? home brew? something else? |
The directory I'm not sure how the mono installation was installed on this machine, I'm guessing an official Mono release since brew doesn't seem to be aware of it. If there's a preferred installation mechanism, I'm happy to nuke the installation on this machine and redo it. |
Does the directory Go ahead and install the latest Mono, either from the official download here, or with Home Brew:
|
Yes the directory |
before you do, could you let me know the output of |
Ok, well that seemed to make the difference (did the brew install of mono). Guess whatever older version of mono I had was problematic. Thanks for walking me through troubleshooting 101 👍 |
Not a problem! Mono has changed the way it lays out on disk a few times. I'm working on making the code that locates the Mono .NET Framework reference assemblies a bit more resilient against this particular install shape. |
FYI, that I've updated the OmniSharp binaries to better locate Mono. If you want to try it (which would be another level of verification for me that I got it right!), you can force the extension to download new runtime dependencies like so:
> rm -rf /Users/mdouglass/.vscode/extensions/ms-vscode.csharp-1.5.0/.debugger
> rm -rf /Users/mdouglass/.vscode/extensions/ms-vscode.csharp-1.5.0/bin
> rm -rf /Users/mdouglass/.vscode/extensions/ms-vscode.csharp-1.5.0/install.lock Then, restart Visual Studio Code, load your project and let the new dependencies download. Of course, I totally understand if you're not willing to be a guinea pig and are happy enough to have things working. 😄 |
Went through those steps and everything seemed to work fine. |
Environment data
dotnet --info
output:VS Code version: 1.7.1
C# Extension version: 1.5.1 (and 1.5)
Steps to reproduce
Just updated to the v1.5 of the plugin with my existing Unity project that uses the VSCode plugin. With that combination the C# plugin stays in the Running state forever when a project is opened and doesn't provide reference information or autocomplete support. I can't attach the project (company confidential unfortunately), but I'll attach the OmniSharp log set to verbose.
If it's helpful, I can try to create a new skeleton project and see if it continues.
omnisharp.txt
The text was updated successfully, but these errors were encountered: