If you’ve been reading these posts through sequentially then I have to congratulate you for making it to the end. If you’ve been reading and following along in your own lab then you get a reverse hi-five plus a harlem shake from me because that’s awesome. You’re a dedicated one.
Now check this out… I was trying to think how I would close this series out but I think I’ll do that with Comment-Based help. In my opinion, this is what separates the armatures from the pro’s because it shows you really care that people know how to use your script. You won’t leave them guessing. Trust me – you don’t want to miss this.
In this post we’ll review the comment based help system. Let’s do it!
When you start to get into scripting you’re going to want to parameterize your scripts because it makes it reusable and professional (not to mention respectable).
In this guide I’m going to show you how to touch up your scripts to make them easier to read. As a rule of thumb, you should never use aliases in your scripts and you should break long lines at commas and pipes.
Technically you could also use a back-tick to break the line but it’s kind of hard to see those back-ticks (even with the font size cranked up) so I stay far from the ticks.
The next four posts in the series are dedicated to scripting. I’m assuming you’ve gone through the 24 posts in this series on learning PowerShell 5. So if you haven’t done that… well you’ve got some reading to do haha.
Today I’m going to walk you through building you very first PowerShell script. This is an exciting time because learning how to write and read PowerShell scripts will make you incredibly valuable to any employer. This is a coveted skill and you’re about to learn it in this post and the next three.