More powershell

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Has anyone ever created a powershell command/script and analysed it in real time, then looked at what actually took place? Kind of like the way you would use Wireshark to analyse data packets over the network?

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Only as far as write-verbose, or write-debug with a debug preference of continue.
Write-verbose, and have that output the current value of a variable at that point of the script, is usually good enough for me.

 

It's worth getting familiar with breakpoints in ISE - then you can check what every variable is at a given point. Can save you hours of troubleshooting, especially with more complicated scripts. Write-verbose is good as well - it just needs typing stuff and I'm too lazy for that.
Both need some practice to use efficiently but worth the effort.

 

Its called a debugger.
https://blogs.technet.microsoft.com...wershell-script-in-visual-studio-code-part-1/

Can get Visual Studio Code here :-
https://code.visualstudio.com/insiders/