The “Hey, Scripting Guys!” blog has been retired. There are many useful posts in this blog, so we keep the blog here for historical reference. However, some information might be very outdated and many of the links might not work anymore.
New PowerShell content is being posted to the PowerShell Community blog where members of the community can create posts by submitting content in the GitHub repository.
Summary: Find all breakpoints for a Windows PowerShell script.
How can I see the debugging breakpoints that are set in my current Windows PowerShell session?
Use the Get-PSBreakpoint cmdlet.
Summary: Ed Wilson, Microsoft Scripting Guy, talks about debugging Windows PowerShell scripts.
Microsoft Scripting Guy, Ed Wilson, is here. One of the cool things about central Florida is there are lots of farmers markets… especially (I am told) this time of the year. This is great, because I prefer organically grown, locally sourced food. I...
Summary: Microsoft PowerShell MVP, Jeff Wouters, talks about using the Get-PSCallStack Windows PowerShell cmdlet.
Microsoft Scripting Guy, Ed Wilson, is here. Today Windows PowerShell MVP, Jeff Wouters, is back with another guest blog post. To read more of Jeff's previous guest posts, see these Hey, Scripting Guy! Blog posts.
And now, Jeff...
...
Summary: Use Windows PowerShell to debug a script on a remote computer. How can I use Windows PowerShell to debug a script on a remote computer? Use the debugging features in the Windows PowerShell 4.0 console:1. Use Enter-PSSession to start an interactive session on the remote computer:PS C: > Enter-PSSession -ComputerName ...
Summary: Learn about remote debugging support in Windows PowerShell 4.0.
Microsoft Scripting Guy, Ed Wilson, is here. Today we have a guest blog written by Paul Higinbotham who is a software design engineer on the Windows PowerShell team…
Windows PowerShell 4.0 includes two major enhancements to the script debugger: script debuggin...