Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

VS Code debugging gets "connect ETIMEDOUT 127.0.0.1:3515" error for UW console/UWP apps #37

Open
ricklee7679 opened this issue May 22, 2021 · 2 comments
Open

VS Code debugging gets "connect ETIMEDOUT 127.0.0.1:3515" error for UW console/UWP apps #37

ricklee7679 opened this issue May 22, 2021 · 2 comments

Comments

@ricklee7679
Copy link

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!
@JohnMasen
Copy link
Owner

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)

@JohnMasen
Copy link
Owner

in order to use the second way(VSCode as server), please add "runAsServer"=false to your launch.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohnMasen @ricklee7679