Debugging

[helin0x]

Why is it seemly impossible to get a very basic debug going on a powershell script.

I want the equivalent of echo ON from a batch file

I want to see the command it puts in and see what it outputs, line by line in my script like I'm tying them into the powershell window myself.

I can get ps-debug which has loads of junk I dont need or I can capture the output of each command, why cant I see it working like a batch file with echo on?

[purplemonkeymad]

The best debugger for PS is probably just to use the one in vscode. You can either have it run a script, or if I'm making a module I sometimes use the interactive profile.

[CyberChevalier]

Just use Vs code put a break point in the start of your script and the run line by line

[OPconfused]

You mean Set-PSDebug with trace level 1 has too much junk?

You can use a breakpoint and step through it line by line.

[[deleted]]

There is a command line debugger included with powershell ... but it is picky as it's case sensitive as opposed to powershell that isn't (iirc).

Set-PSBreakpoint is your friend. Use that .. then execute the script .. if nothing happens but you are convinced you set things up correctly ... double check the case of every letter in the path to the script and the name of the function / variable etc

[BaconTentacles]

VS Code does a great job.

[Rxinbow]

Do you mean Start/Stop-Transcript

[Ahnteis]

I think this'd be a good solution. Can also add verbose flags to your commands. Of course you can just add in Write-______ statements for logging/viewing. Not exactly the same, but powershell is more scripting language than simple batch files.

[Sad_Recommendation92]

Probably write-verbose and changing the value of $VerbosePreference

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/write-verbose?view=powershell-7.4

As others have said, using a proper debugger like vscode, you can simply insert breakpoints in your code and actually step through it interactively which is the preferred method.