-
Notifications
You must be signed in to change notification settings - Fork 481
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
Problems getting the debug system to behave #746
Comments
You shouldn't have a different experience when opening more than one file, the debugger will only launch the currently active file when using the "current file" configuration. Can you attach logs from a session where the debugger exhibits this behavior? https://github.com/PowerShell/vscode-powershell#reporting-problems |
@johnbeh I'd like to take a look at this issue soon, could you capture and attach (or send via email) your logs so that I can take a look? https://github.com/PowerShell/vscode-powershell#reporting-problems |
Sorry not to have commented earlier. Just as an aside - I am very pleased and grateful for the tremendous efforts that are going on with this project. Thank you all very much. Regards John |
Thanks for the kind words John, glad the issue has been resolved for you! Let us know if you see anything similar again :) |
System Details
$PSVersionTable
:Issue Description
DEBUG
I can't persuade the F5 on the standard install to behave anything like sensibly. If I have ONE PS1 file open it will run sensibly.
If I have a second file open it doesn't run at all. The little blue line just under the DEBUG line and above the VARIABLES section moves back and forward for ever. I've given it 10 minutes to run a script that the POWESHELL ISE runs in 2 or 3 seconds.
It seems that this is solved by changing the Version in Launch.json from
"version": "0.2.0", to
"version": "0.1.0",
BUT this can't possibly be the right answer although it suffices for the moment
Attached Logs
Follow the instructions in the README
about capturing and sending logs.
The text was updated successfully, but these errors were encountered: