Learn PowerShell Scripting in a Month of Lunches, Second Edition

9 Avoiding bugs: Start with a command

Before ever firing a script editor, we start in the basic PowerShell command-line window. This is your lowest common denominator for testing, and it’s a perfect way to ensure the commands your tool will run are correct. It’s way easier to debug or troubleshoot a single command from an interactive console than debugging an entire script. By “a single command,” we mean a PowerShell expression—a single thing that we can manually type into the console to see if we’ve got the correct syntax. You’ll start to notice a theme from here on out. Start small (with a single command), get that working, and start building from there. Don’t try to write your entire script all at once. This will make it almost impossible ...