Reset Session before launching debugger

[Hypernut]

I love the fact that after having run a script via the debugger, the variables and objects are still available in the console.
But launching the debugger again, does not reset the session as well, what can cause unintended side effects, due to stuff created in the session like background jobs, variables, other runspaces and so on.

This is such an big obvious problem for me that I do wonder why nobody seems to bother, which in turn makes me think: do I simply use it wrong? :)
But I am not aware of any way to remove, clear and close really everything than can be created, opened or assigned in a PoSh-Session, to avoid any potential problems, other than: killing the terminal manually and lauching a new session.

So I would like the option that every time the debugger is launched it either resets the session or creates a new one (an killing the old).

[corbob]

The setting powershell.debugging.createTemporaryIntegratedConsole isn't exactly what you're asking for, but it does create a temporary console that lasts just for the run of the debugger.

That being said, I think it would be helpful to have an option that spins up a new console that stays around until the next debugging session (I also have no idea how that would work).

[Hypernut]

No, unfortunately the temporary console does not allow interactive debugging and is therefore -at leat to me- useless.

[corbob]

I must be confused by what you mean by interactive debugging. In the stable extension I am able to use a temporary session and debug the script:

The session doesn't stay active, but the terminal window does until you start another debug.

[corbob]

Ignore what I posted there. I just saw #1263 while submitting a bug where the preview is failing (looks like log permissions). What I didn't try was actually doing stuff in the terminal while at a break point. It appears you can only do a single command and then nothing else in the terminal.

[TylerLeonhardt]

This is fixed in the next release that'll happen this week.

[Hypernut]

If you mean v2020.1.0 by "next release" then it is not.

[TylerLeonhardt]

I was referring to @corbob's issue about the log file permissions.