Debugging Powershell scripts

[sg08234]

Can I debug Powershell scripts? In my (v24-)version on debug my standard Editor is opened when I try to debug.

Should I switch to v28?

Thanks - Michael

 

[drwtsn32]

VS Code is the best powershell script debugger!

 

[sg08234]

Thanks : Might well be but I am looking for a "universal" (Batch and Powershell) debugger.

 

[Joe Caverly]

This .btm file will launch your PowerShell Script in the PowerShell ISE for debugging...

@setlocal
@echo off

echo Generating Powershell Script...

type <<- endtext > psise.ps1
Write-Host Good Day!
(get-date).tostring()
endtext

echo Launching Powershell Script in Debugger...

powershell_ise psise.ps1

echo All done!
endlocal

You can even launch your .btm via the TCC Debugger...

bdebugger psise.btm

...which will then launch the PowerShell ISE to debug your PowerShell Script, and then return to the TCC debugger to finish debugging the .btm.

Joe

 

[sg08234]

Thanks but this "only" ist a shortcut to Powershell ISE with the disadavantage that I have to copy with two different debug tools.

BTW: The same holds tru if i switch to VS Code for Powershell debugging.

I obviously have to live with two different debug tools.

Michael

 

[drwtsn32]

two different debug tools

I was curious if VS Code could debug regular batch files. I found this which links back to JP Soft lol.

 

[sg08234]

Strange - Bat as mentiones above: I obviously have to live with two different debug tools.

 

[Joe Caverly]

In VS Code, I use an extension called Batch Runner.

I've contacted the author of the extension,

regarding better integration with TCC-RT,

and am hopeful that he will consider my suggestion.

Joe

 

[sg08234]

Thanks

 

[AnrDaemon]

I don't know a debugger that could debug two contexts at once.
Even VS Code will only run one debugger of all the configured ones.

 

[sg08234]

Must not be at once: Should be the same because of the learning curve.