![Step 3 - Created the output parsers](https://sdwheeler.github.io/seanonit/images/crescendo/slide07.png?v=3b8889b7c09db86354d6937d80f92635)
- Crescendo doesn’t make this part any easier, but it does allow you to focus on parsing the output
- I started with the parsing functions because I was more comfortable writing PowerShell than JSON
- I captured the output of each subcommand into a text file that I could easily use as input to my parsing function
- Let’s step through an example for parsing the output from vssadmin list shadows
- Here is the output of the native command
- Notice how the labels and data are presented
- Set breakpoints on first line and Original Volume line
- Step through first line
- Notice that I convert the string to a GUID object
- Remove break point and run until next breakpoint
- See how the line is subdivided into multiple property values
- Remove all breakpoints and show the output as objects
- Switch to terminal and show the verbose output
- Jim, what is I am having trouble? How can I see what native command is actually being run?