JohnMasen
VS Code debugging gets "connect ETIMEDOUT 127.0.0.1:3515" error for UW console/UWP apps
I am able to debug in VS Code for console application targeting .NET Core 2.1 (similar to the RunScript example project's) , but getting "connect ETIMEDOUT 127.0.0.1:3515", when running the same codes (c#/javascript) in a Universal Windows console app or UWP app. Does VS DebuggerAdapter work with UWP applications? Thanks!
UWP does not allow connect/listen to localhost by default. you might need enable localhost loopback. src/Tools/RunScript/Program.cs line 60 demonstrates another debug way, instead of listen to 3515, engine will connect to VSCode(you need to start debug in VSCode first)
in order to use the second way(VSCode as server), please add "runAsServer"=false to your launch.json