-
Notifications
You must be signed in to change notification settings - Fork 513
Support stopAtEntry #115
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
Comments
Funny, GitHub has post reactions now. But yeah, sounds good! I guess we can just add a breakpoint at line 1 of the file. Not sure if PowerShell has a different way to accomplish that, but this seems like a reasonable approach. |
Wonders never cease! :-) |
I feel like this is relatively trivial, maybe? |
Just to give some context to anyone willing to pick this up, I think this is just a matter of:
To add a breakpoint on line one that function, you can likely use the |
Hey everyone, I think I'm gonna take this one up! |
Should we support something like this for debugging:
Stop at Entry
Setting the stopAtEntry flag will cause the debugger to break immediately on the entry point to the application. This allows you to start stepping through your code without setting breakpoints.
The text was updated successfully, but these errors were encountered: