[OSX] No intellisense, strange editor path?

[raldred]

I've just done a fresh install of OSX El Cap. Unity 5.3.4f1 VSCode latest 1.1.1 (13th May) Running the latest 2.6 Release of plugin

Editor path for preferences has as weird path for Code. Plugin keeps prompting for debugger install even though I have it installed.

External tools preferences

VSCode preferences

Extensions Installed

Debugger installed

Tried reinstalling everything & cleaning out .csproj & .sln files can't get intellisense to work. I notice there's no -CSharp.sln being generated?

Project folder

I had everything working nicely on Yosemite but needed upgrade to El Cap for latest XCode & I always do a fresh OS install instead of an update.

Any suggestions much appreciated

[Souk21]

It's because of the new C# extension version.

You can just uninstall "C# Extension" for the moment, and re-instal the old "Built-in Omnisharp" which should work.

[seanmcbreen]

Thats right we apologize for this - we have added some additional context re: this to the VS code unity page. We are also working with the C# team to ensure support is added to the new C# plug-in.

Updated doc for VS Code and Unity

cc' @reapazor

Sean -VS Code Core Team Member

[corum]

Same issues here but, at the moment of writing, it seems impossible to install the legacy Omnisharp extension under Windows. I just have syntax highlighting and no Unity related intellisense, except for literal (abc) one.

[LiGoEX]

Have the same problem too!Legacy c# extension has been installed,and the Mono has been updated but the intellisense still won't show up!Any solution now?

[raldred]

Installed legacy c# and working fine, full unity intellisense. Make sure you remove the latest c# extension first

[corum]

I can only confirm that, under Windows 8.1 pro x64 and Visual Studio 2015 PE, VSCode intellisense for Unity is totally broken.

[jlmakes]

@raldred Intellisense is working with Enums for you?

[raldred]

@jlmakes yes working fine