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 to debug.

9.1 What you need to run

If you’ve already read the previous chapter, then you know that in the example scenario, you’ve been asked to develop a tool that will query the following information:

9.2 Breaking it down, and running it right

9.3 Running commands and digging deeper

9.4 Process matters

9.5 Know what you need

9.6 Your turn

9.6.1 Start here

9.6.2 Your task

9.6.3 Our take

Summary