To be fair I've spent more time writing this post than testing that though, so I might come up with something later.Īll in all I haven't done any heavyweight testing, but scratching the surface it seems to work good enough for me to try to switch from MonoDevelop at least. It seems like VSC is able to attach to running Mono instances (configurable in launch.json), but I can't manage to make it connect. It does however properly immediately red-underline it when you try to use it, with a proper tooltip error. The intellisense is somewhat more liberal with what to show, for example its shows deprecated fields & members without really telling. It seems to work fine to me, and is a lot faster than MonoDevelop. Note you will still need to open your project manually in VSC, but this will at least allow you to open a specific script file from within Unity once you've done that. In Unity's preferences, select VSC in External Tools->External Script Editor. You can click it and select one of the projects.

Select 'File->Open' in VSC and open the root folder of your Unity projectĪt the bottom left, in your VSC status bar, there should be a small flame icon with the label '2 projects' or similar next to it.

(I installed it using homebrew, with 'brew install mono'.) This is for the intellisense engine in VSC to work. The few simple steps I took (on Mac) was:

I've managed to get VSC working as a code editor with proper intellisense, but I have not yet been able to attach it as a debugger (although I feel that should be possible as well). I haven't found a lot of info about running Unit圓D with the newly released Visual Studio Code, so I thought I'd share what I've found out so far by testing a bit.

Visual studio mac unity red underline