Visual Studio Code

It always hang, when attempt to "Step Into" through property of objects without source code (for example List<T>.Count).

 

To build Unity in Visual Studio Code, you can hook up Mono xbuild compiler as a task runner, so you don't even have to leave IDE to have errors and warnings (kind of workaround to have the syntax properly checked).

See https://twitter.com/_eppz/status/846859856787259392 for more.

 

For windows users -> path (with default Unity install) to xbuild is:
"C:/Program Files/Unity/Editor/Data/Mono/bin/xbuild.bat"

 

Also, check eppz! (C# theme for Unity).

 

Did anyone manage to get VS Code to work with Unity while using the .Net 4.6 scripting preview?
I find that as soon as I switch to .Net 4.6 VS Code won't show scripting errors anymore. Neither does intellisense or debugging seem to work. If I attache Unity and start debugging, Unity will either ignore breakpoints or crash completely on play.

 

worked for me. you are using the insiders version with updated extensions?
https://code.visualstudio.com/insiders

 

VS Code is great! I just have one missing feature if anyone knows how to fix it.
I would like it to understand #if preprocessor definitions.
EG: When I have some code like this and I work in Standalone Windows.

Code (CSharp):

1. #if UNITY_PS4
2. //hello ps4
3. #elif UNITY_STANDALONE
4. //hello pc
5. #endif

It does not gray out the PS4 code.
How can I do this?