Hi, I’m a developer, and I hate PowerShell*. For no reason in particular, PowerShell just never seemed that appealing for me as a developer, as it was always marketed towards sysadmins. And I never liked the syntax – all those dollar signs reminded me of PHP.
This recently changed, however. A client had a set of legacy perl scripts which nobody could maintain anymore – and I was tasked with rewriting them. Having recently spent some time writing a script for Boxstarter – an amazing tool that allows you to automate software and environment installations of new machines, powered by Chocolatey, in PowerShell, I thought that it could be a good fit for the task. I knew the language is powerful enough to allow the creation of those very useful tools, so I decided to give it a shot. I was not disappointed!
Luckily, you already have all the tools you need to get started! Every Windows machine comes with both PowerShell and PowerShell ISE (Integrated Scripting Environment) already installed.
Here’s what you need to know about PowerShell:
You can do most of your development and debugging in the ISE – no need to type individual instructions in the PowerShell console. It’s great as a REPL, but nothing beats an IDE. Tip: select a few lines in the ISE and press F8 – only those lines will be executed!
It’s dynamic – every variable can be treated as anything, but also support explicit typing (which are checked at runtime). Variables are prefixed with the
It’s pipelined – every variable or the output of every function can be piped as an input to another function using the pipe (
|) operator. It’s extremely useful when dealing with collections and other enumerable objects – allowing you to filter the elements and transform the result into whatever you need.
It supports everything you know from .NET – although PowerShell defines its own idioms with regards to common operations, such as formatting strings for joining paths, you can use all objects from .NET to do the same thing.
It’s concise – everything in PowerShell can be verbose or very concise. By leveraging aliases there are many ways to say what you mean. Here’s an example: the following function gets a list of changed files between two SVN revisions, by executing the svn diff command, outputting the result as XML which looks like this:
This XML is stored into an
$output object, which is defined as a .NET
XmlDocument. The object is than being queried via XPath to get only items of kind ˜file’ which are ˜modified’. Finally, only the text of the node is selected.
Quite a lot is going on in this example, which demonstrate the Power of PowerShell:
- A process is started with the
&symbol. Can also be started with Start-Process for more options.
- Strings can be formatted with
-f, however in this case they are a part of an expression, and have to be escaped into their own expression by using
%symbol is an alias of
foreach, which is an alias of
Get-Alias -Definition ForEach-Objectto see all the alias definitions, or
Get-Alias %, for example.
- The last line in a function (or selection) is what gets returned (or printed out). In this case, the result of the last line is a single string, containing the value *˜other.txt’ (it’s the only modified file). If there was more than one result, the return would be an array.
- Finally, to call this method, we use
Get-SvnDiff 1000 2000, and we can use the pipe operator (
|) to continue modifying the returned values.
And that’s it! Sure, there is way more to know about PowerShell, but this should be more than enough to get started, or at least, not to get lost when reading and writing simple scripts.
*Well, slightly less now.