search

microsoft / nodejstools

Node.js Tools for Visual Studio
http://aka.ms/explorentvs
Apache License 2.0
1.79k stars 359 forks source link

NodeJS command line app result window closes immediately #1998

Open rajakondla opened 6 years ago

rajakondla commented 6 years ago
Expected Behavior
Actual Behavior
Steps to Reproduce

I am using vs 2017 community edition. I am new to nodeJS with TypeScript. I have created nodeJS TypeScript command line application. The result window is closing immediately after running the application. I have tried checking the check box (Wait for input when process exits normally under Tools->options->nodeJS tools) but still window closes immediately. Please suggest if I am missing anything.

paulvanbrenk commented 6 years ago

Yes, we're investigating how to re-enable that checkbox for node 8 (and newer). YOu should be able to set a breakpoint and have the program stop that way.

paulvanbrenk commented 6 years ago

Yes, we're investigating how to re-enable that checkbox for node 8 (and newer). YOu should be able to set a breakpoint and have the program stop that way.

amcasey commented 5 years ago

@jessetrinity If this still repros, we probably just need to adjust the arguments to our PressAnyKey exe.

jessetrinity commented 5 years ago

It doesn't look like the PressAnyKey process is even being started when debugging. It does launch and respect the options when 'Start Without Debugging (Ctrl + F5)' is selected. I will keep looking to see what can be done in the former case.

paulvanbrenk commented 5 years ago

Last time I looked at this, this was something that needs to be handled in the debugger code.

From: Jesse Trinity notifications@github.com Sent: Wednesday, April 10, 2019 6:18:13 PM To: Microsoft/nodejstools Cc: Paul van Brenk; Comment Subject: Re: [Microsoft/nodejstools] NodeJS command line app result window closes immediately (#1998)

It doesn't look like the PressAnyKey process is even being started when debugging. It does launch and respect the options when 'Start Without Debugging (Ctrl + F5)' is selected. I will keep looking to see what can be done in the former case.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/nodejstools/issues/1998#issuecomment-481887569, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFB5d1eRO47oz8-N725LUEwEk7HKOe7Fks5vfmMlgaJpZM4VGYgV.

Scampi-ml commented 1 year ago

Ive had "C:\Program Files\nodejs\node.exe" checked as "Run this program as an administrator" for an issue. Unchecked the box => fixed

pkropachev commented 11 months ago

Is there any news regarding this issue? I still observe the problem in Visual Studio 2022 (17.7.0) for NodeJS console apps.

alessiot89 commented 8 months ago

this thing is still bugged.