Search Unity

Vscode Pain Points - Bugs Or Just Not Supported?

Discussion in 'Code Editors & IDEs' started by Sam-Sproutel, Apr 11, 2019.

  1. Sam-Sproutel

    Sam-Sproutel

    Joined:
    Jun 4, 2018
    Posts:
    5
    In are day to day, we have been running into some pain points using VSCode on Mac and Windows:
    • Debugging
      • Issues with breaking into code via a breakpoint.
      • Inspecting variables.
      • Not being able to modify and set properties at debug time.
      • Not being able to evaluating pieces of complex conditionals at debug time
      • Unable to effectively step into anonymous functions
      • Issues with conditional breakpoints being flaky
    • csproj becoming out of since and causing weirdness with Omnisharp and Intellisense. Caused by:
      • Moving scripts
      • Renaming scripts
      • Changing the namespace of scripts
    Posting here because I'm not sure where to raise the issue, or if this is an issue at all. Its possible that these features could be missing or in development? Does anyone else experience this?

    Also interested getting the communities feel on the matter and hoping some of Unity's engineers will chime in too!
     
    joelatsproutel likes this.