Microsoft’s PowerShell is radically different than shells on UNIX or GNU Linux systems in that Powershell can deal in objects rather than just plain text.
A concrete example may help you more quickly understand the difference. Suppose you want to get and save information about all the files in a certain subdirectory. We want to get not only the names of the files but as much metadata as possible relating to each file such as date of creation, date of modification, etc. This information also needs to be stored in a single XML document. To keep the size of this post manageable, our subdirectory contains only two files, i.e. file.xml and file.xsl, as shown below.
On a UNIX or GNU Linux system, this would be a somewhat difficult task to quickly accomplish. Using Powershell, however, it becomes a simple one or two line task.
Because Powershell is fundamentally object-orientated, it regards a filesystem as being an object representated as a location exposed by provider. More generally, a location can be a file directory, a registry hive, a certificate store or some other “thing” exposed by a provider. The Powershell get-childItem cmdLet is used to retrieve information, including metadata, about items in a specified location. Thus get-childItem can be used for a lot of different types of operations including enumerating directory contents, listing registry values or showing the current values of variables. For our purposes, get-childItem exposes information about files in a specified subdirectory or the current directory if no directory is specified.
Here is a single line Powershell script which does what we want to do. It retrieves metadata about the two files in the current directory using the get-childItem cmdLet, pipes that data to a cmdLet called ConvertTo-XML which in turn converts the metadata into a valid XML document. The save method is then used to write this stream out to a file called file.out in the current directory. (get-childItem | ConvertTo-XML -NoTypeInformation).save(“$(convert-path “X:”)\file.out”)
Alternatively, we could store the retrieved metadata in a variable and then write it out to a file as shown below. Similar to bash and ksh93, Powershell supports the concept of aliases and defines ls as one of the aliases for the get-childItem cmdLet,dir and gci being the other two. $a=(ls | ConvertTo-XML) $a.save(“$(convert-path “X:”)\file.out”)
Here is the contents of file.out. As you can see, quite a bit of information about each of the two files is exposed. <?xml version="1.0"?> <Objects> <Object Type="System.IO.FileInfo">