Chapter 9. Avoiding bugs: start with a command
Before we ever fire up 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 make sure the commands your tool will run are correct. It’s way easier to debug or troubleshoot a single command from an interactive console than it is to debug an entire script. And 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 right syntax.
This is by design
One of the cool parts about PowerShell is that you can open a console, run commands, and get immediate results (or errors). Traditionally, programmers have had to write code as best they could, compile it, and possibly even code up a test harness so that they could test their code. Take advantage of PowerShell’s immediacy to reduce your overall workload!
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-: