Skip to main content

Effective Windows PowerShell free ebook

A late Christmas gift for everyone,  Keith Hill has turned a set of blog posts into an 61 pages long PowerShell ebook.

Download your own copy here.

 

Table of content:

  • Introduction
  • Item 1: Four Cmdlets that are the Keys to Discovery within PowerShell
    • Key #1: Get-Command
    • #2: Get-Help
    • Key #3: Get-Member
    • Key #4: Get-PSDrive
    • PowerShell 2.0 Update
  • Item 2: Understanding Output
    • Output is Always a .NET Object
    • Function Output Consists of Everything That Isn't Captured
    • Other Types of Output That Can't Be Captured
  • Item 3: Know What Objects Are Flowing Down the Pipeline
  • Item 4: Output Cardinality - Scalars, Collections and Empty Sets - Oh My!
    • Working with Scalars
    • Working with Collections
    • Working with Empty Sets
  • Item 5: Use the Objects, Luke. Use the Objects!
  • Item 6: Know Your Output Formatters
  • Item 7: Understanding PowerShell Parsing Modes
  • Item 8: Understanding ByPropertyName Pipeline Bound Parameters
  • Item 9: Understanding ByValue Pipeline Bound Parameters
  • Item 10: Error Handling
    • Terminating Errors
    • Non-terminating Errors
    • Error Variables
    • Working with Non-Terminating Errors
    • Handling Terminating Errors
    • Trap Statement
    • Try / Catch / Finally
  • Item 11: Regular Expressions - One of the Power Tools in PowerShell
    • PowerShell 2.0 Update
  • Item 12: Comparing Arrays
  • Item 13: Use Set-PSDebug -Strict In Your Scripts – Religiously
    • PowerShell 2.0 Update
  • Item 14: Commenting Out Lines in a Script File
    • PowerShell 2.0 Update
  • Item 15: Using the Output Field Separator Variable $OFS
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more