I am tracking notes on PowerShell in PS1 files on my git hub repository. You can see all 100 days of code entries on the blog category page.
As at least inferred on my Day 0 post, a lot this PowerShell stuff will be in the context of re-writing the advib utility (more on this in days to come).
Today I started going through chapter 4 of Learn Windows PowerShell in a Month of Lunches trying to follow “try it now” type areas and taking further notes on the areas I previously gone through with a highlighter.
I do like that Show-Command option: it’s kind of a GUI walk through of setting up a command and you can copy the command as a line to the clip board. Seems like a good way to learn.
Unlike the book, I think I’m going to use cmd /c for commands I know aren’t designed and/or won’t work in PS. I don’t think those commands can be piped anyway. The book suggests the “stop parsing” symbol. This may come in use later, but for normal commands I’ll stick with cmd /c unless I find a reason not to.