GS2: Three Key PowerShell Commands

江湖浪人

　　Here are three simple, yet key commands, which are designed to get you started with PowerShell. As you study these cmdlets, keep in mind the golden rule, verb-noun, for example, get-PSProvider.
　　Three Key PowerShell Commands or Cmdlets

• Get-Command
  
• Get-Help
  
• Get-Member
  

　　1. Get-Command
　　Let us begin by testing get-Command. What this instruction does is list all of PowerShell's noun-verb pairs, which are also referred to as built-in cmdlets. Assuming that you have opened a PowerShell session, then you should see a prompt like:
　　PS > Now type: get-command
　　To filter the list, employ the famous star * wildcard; here are three examples:
　　get-Command out*
　　get-Command add*
　　get-Command get-*
　　Let us experiment with a variation of this wildcard theme which displays only cmdlets beginning with the verb 'set':
　　get-Command set* -commandType cmdlet
　　It is possible to tweak the display of your output columns with ft (Format-Table). My hidden agenda here is to give you practice with PowerShell's Pipe symbol (|), try:
　　get-command |ft name, definition –auto
　　At the moment we are just 'playing', testing, or feeling our way, thus do feel free to experiment with your own ariations of my suggestions. Once you have seen the long list of all possible commands, chose one example for further research, for example:
　　Get-PSProvider (Or plain: PSProvider)
　　This is what happened when I typed just:
　　get-Psprovider

　　Challenge: try
　　PSProvider | get-member
　　Another Command PSSnapin What PSSnapin does is reveal the sources for the built-in cmdlets:
　　Get-PSSnapin
　　Or
　　Get-PSSnapin |ft name, description –autosize

　　Note how every PowerShell noun is singular, PSSnapin, Command and PSProvider. Also note how a Pipe (|) followed by ft means format the output as a table, as opposed to format the results as a list(fl). Any words which follow 'ft' are names of the fields, each separated by a comma. At the end of the above command is the switch -autosize, this extra parameter tells PowerShell to close-up the>　　-auto
　　In the example below, I have used ft to omit the Description field and just displayed the name:
　　Get-PSSnapin |ft name
　　2. Get-Help
　　Avoid arrogance, put aside pride,  and call for PowerShell's built-in help. We all have to learn somewhere and only you know what you type in the privacy of your PowerShell command line.
　　Perhaps what puts us off trying built-in help is a bad experience with the stilted help of an old DOS system. Dare I suggest that experience with internet search techniques makes us more willing to try a modern application's own help?
　　PowerShell's help has some interesting switches, such as: -full and -example. Incidentally, -exampleS also works, a rare case of a plural PowerShell noun.
　　Get-help get-wmiobject
　　Note: Get-help does not require the pipe symbol. In fact, the pipe (|) only gets in the way of gethelp; Powershell does its best to interpret: Get-help | get-wmiobject cim_chip But it still results in an error, therefore stick with plain simple: Get-help get-wmiobject
　　PowerShell’s Hidden ‘About’ files
　　In the PowerShell folder, referenced by: $PSHome **, you will find a whole family of About help files. In these files, which all begin with About_, you will discover information on topics such as Foreach, If and ElseIf. My point is that you cannot get assistance by typing: get-help foreach, yet you can find a wealth of information if you read the file at: $PSHome\about_foreach.help.txt **.
　　Here is a cmdlet that reveals the names of these About files:
　　# List all the About help files
　　$i=0
　　$Homes = get-ChildItem "$PSHome\about*. *" -recurse
　　foreach ($About in $Homes) {$About.name; $i++}
　　"There are $i about files"
　　Result: A list of 55 files. (The precise number vary with each version of PowerShell)
　　** On my system $PSHome translated to: C:\WINDOWS\system32\WindowsPowerShell\v1.0
　　3. Get-Member
　　Learn from mistakes my mistakes, and take a minute to imprint the format of this get-member command into your brain. The key point is that the object you want information about comes at the beginning, and not at the end of the command. My second error was (is) forgetting the pipe symbol.
　　Here is the correct format:
　　Get-process | get-member
　　Wrong
　　get-member | get-process (sequence incorrect)
　　get-process get-member (forgot the pipe symbol)
　　Worth a try:
　　Get-process | Get-member -membertype property
　　Get-process | Get-member -membertype method

　　Call me lazy, or call me showing that commands are not case sensitive. My point is that get-Process, Get-Process and get-process are all interpreted>　　Tab Completion
　　Talking of being lazy, PowerShell also supports a tab auto-complete feature. Once you have typed enough of a command to make it unique, you can press tab and PowerShell completes the rest of the command.
　　get-process get-mem(tab) automatically expands to: get-process get-Member. As you can probably guess, this tab completion works for all commands not just this one. Incidentally, when you employ PowerShell's parameters you can take advantage of a similar automatic completion, for example - auto instead of -autosize and -f instead of -filter. Once again, there are many more such autocompletions.
　　Summary of PowerShell's Commands
　　Talk to an experienced PowerShell user, or talk to a teaching guru, they will each tell you that that the secret of success is simple, keep returning to the basics until you gain mastery. Those basics are:
　　get-command
　　get-help
　　get-member