S sg08234 Nov 33 0 Nov 13, 2022 #1 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
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
S sg08234 Nov 33 0 Nov 14, 2022 #3 Thanks : Might well be but I am looking for a "universal" (Batch and Powershell) debugger.
Joe Caverly Aug 1,933 71 Nov 14, 2022 #4 This .btm file will launch your PowerShell Script in the PowerShell ISE for debugging... Code: @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... Code: 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
This .btm file will launch your PowerShell Script in the PowerShell ISE for debugging... Code: @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... Code: 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
S sg08234 Nov 33 0 Nov 14, 2022 #5 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
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
D drwtsn32 May 550 6 Nov 14, 2022 #6 sg08234 said: two different debug tools Click to expand... I was curious if VS Code could debug regular batch files. I found this which links back to JP Soft lol.
sg08234 said: two different debug tools Click to expand... I was curious if VS Code could debug regular batch files. I found this which links back to JP Soft lol.
S sg08234 Nov 33 0 Nov 14, 2022 #7 Strange - Bat as mentiones above: I obviously have to live with two different debug tools.
Joe Caverly Aug 1,933 71 Nov 15, 2022 #8 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
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
A AnrDaemon Aug 728 10 Nov 18, 2022 #10 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.
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.
S sg08234 Nov 33 0 Nov 18, 2022 #11 Must not be at once: Should be the same because of the learning curve.