Any output from any PowerShell cmdlet or script is sent to the pipeline, we will look at this in more detail in the next section, the pipeline has some default settings and so if you don’t tell PowerShell where to send what’s on the pipeline it will use it’s default settings.<\/p>\n\n\n\n
The default output is normally your screen or console.<\/p>\n\n\n\n
PowerShell also does not output text. It may look that way but what it actually puts on the pipeline are objects. An object is just a data structure that consists of one or more things. You can think of it in terms of a database record with a number of fields and values. Your output could be more than one record, a collection of records if you like. In PowerShell they refer to it simply as a collection.<\/p>\n\n\n\n
What does this look like in a PowerShell and how do we know what kind of object is returned? Well we got back to our old friend Get-Member<\/code> <\/p>\n\n\n\n
The first thing we see returned from the Get-Member output is the type of object the command returns<\/p>\n\n\n\nPowerShell console showing a cropped output of Get-Process piped to Get-Member showing the returned object type <\/figcaption><\/figure>\n\n\n\n
Then we get all the “field names” and “datatypes” just like we would have in a database for each record, or maybe for each row in a spreadsheet, I couldn’t fit them all in one screen so here is a sample?:<\/p>\n\n\n\nPowershell console showing cropped output of Get-Process when piped into Get-Member. It lists some of the members of Get-Process<\/figcaption><\/figure>\n\n\n\n
The Get-Process cmdlet has 92 different methods, properties, sets or aliases in its object type System.Diagnostics.Process<\/p>\n\n\n\nAn Image showing the summation of member types in object System.Diagnostics.Process<\/figcaption><\/figure>\n\n\n\n
OK, so an object can have one or more parts to it what are those parts?<\/p>\n\n\n\n
Property <\/strong>– This is what holds the value, the actual data we want.<\/li>
Method<\/strong> – An action that can be performed on the object <\/li>
ScriptProperty<\/strong> – these are used to calculate property values<\/li>
AliasProperty<\/strong> – As its names suggest, it is an alias to another property<\/li>
Event <\/strong>– These are .NET events linked to the object.<\/li>
PropertySet <\/strong>– Unsurprisingly, it holds a set of properties.<\/li>
NoteProperty<\/strong> – Simply hold static property names<\/li><\/ul>\n\n\n\n
Let’s look at these in a bit more detail<\/p>\n\n\n\n
Property<\/h2>\n\n\n\n
It holds some data of a predefined type. Property data types are often things like strings, integers, boolean or datetime and they are the data or values that we normally want to see when we run our cmdlet. Name, state, version are all examples of a property<\/p>\n\n\n\n
Method<\/h2>\n\n\n\n
This is something we don’t use much as we start out with PowerShell, but you will find you use more as you become more familiar with them.<\/p>\n\n\n\n
Let’s look at the output of Get-Member where we filter only the Methods. there are some that should be obvious, kill, close, refresh, start. These are all called by adding them to the end of the cmdlet<\/p>\n\n\n\nImage of PowerShell console showing members of Get-Process with a MemberType of Method<\/figcaption><\/figure>\n\n\n\n
Try this practical example:<\/p>\n\n\n\n
\n
\n
\n
\n
Start notepad <\/li>
Open PowerShell<\/li>
Run the command get-process -name notepad <\/code><\/li>
Review the output, you should see the notepad process<\/li>
Run the command (get-process -name notepad).kill()<\/code><\/li>
Run the command get-process -name notepad <\/code>again<\/li><\/ol>\n\n\n\n
The notepad process no longer exists, you used the kill<\/code> method to stop it from running, the image below shows this in my console:<\/p>\n\n\n\nImage of a PowerShell Console showing the process details for a process named Notepad<\/figcaption><\/figure>\n\n\n\n
Alias<\/h2>\n\n\n\n
Those used to BASH will understand the concept of aliases. If you haven’t come across them before they are simply an alternate name for an existing thing often a command or property. PowerShell has a number of built in aliases for the lazy amongst us, we discussed some in the last lesson. <\/p>\n\n\n\n
Select<\/code> is an alias for Select-Object <\/code> <\/li>
Where<\/code> is an alias for Where-Object<\/code><\/li><\/ul>\n\n\n\n
There are other as well, ls<\/code> and dir<\/code> are both aliases for Get-Childitem<\/code><\/p>\n\n\n\n
In an object the alias property usually points to an other property. We can investigate this in our Get-Process<\/code> command by looking at what they point to. Call Get-Member<\/code> again but this time look at the member type aliasproperty<\/code><\/p>\n\n\n\nImage of a PowerShell console shooing the member of Get-Process with a MemberType of AliasProperty<\/figcaption><\/figure>\n\n\n\n
Lets look at the first couple of these:<\/p>\n\n\n\n
Handles<\/strong> is an alias for HandleCount<\/strong><\/li>
Name<\/strong> is an alias for ProcessName<\/strong><\/li><\/ul>\n\n\n\n
this simply means we can get the same output using the shorter aliases<\/p>\n\n\n\nImage of a PowerShell console showing get-process using alias members and property members producing the same result <\/figcaption><\/figure>\n\n\n\n
Summary<\/h2>\n\n\n\n
Output from any PowerShell cmdlet or script is sent to the pipeline, if you don’t specify differently, it is eventually sent to the default output devices which is normally the console<\/p>\n\n\n\n
Output is in the form of objects<\/p>\n\n\n\n
Objects are collections of members (these are more commonly referred to as properties but this can get confusing)<\/p>\n\n\n\n
Members have different types. Method, Property and Alias are the ones you’ll use the most.<\/p>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div><\/div>\n\n\n\n
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-10.png\")
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-11.png\")
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-12.png\")
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-13.png\")
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-15.png\")
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-16.png\")
![\"\"](\"http:\/\/vroamam.com\/wordpress\/wp-content\/uploads\/2021\/08\/image-17.png\")