-
Notifications
You must be signed in to change notification settings - Fork 357
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.
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
issue with debugging #199
Comments
Did you try the latest Dev build? https://github.com/Microsoft/nodejstools/releases Fixes a race condition in debugging that caused similar symptoms |
I too have had this issue, it's almost as if Node itself doesn't "kick-in" as it's very early in the debugging loading or scheduling of the run... Sometimes rebooting VS works, but other times after a full day of debugging i have to reboot computer to regain control over NODE |
Have you tried the latest Dev build I linked to above? |
Has not tried yet, I have to finish my project. |
Is there a dev build available for VS 2013 too? Not all companies run their development on Beta IDEs |
@pke yes, see the downloads in the link above. We currently have Dev builds available for 2012, 2013, and 2015. |
Closing this issue as a duplicate. Please post at #246 if you're still running into issues with the latest builds. |
From time to time, when i start debug my application, after pressing on F5 or Start Debugging, the debug started and seems that the program running, but it not running (i have some console.log() prints lines in a code, nothing printing in cmd) and not stopping on breakpoints at all.
After restarting of visual studio, its run and debugging work perfectly
My machine is:
win8.1 64bit
vs2013 premium Update 4
Best Regard
Denis
The text was updated successfully, but these errors were encountered: