You're reading from PowerShell 7 Workshop Learn how to program with PowerShell 7 on Windows, Linux, and the Raspberry Pi

Product type Paperback

Published in Feb 2024

Publisher Packt

ISBN-13 9781801812986

Length 468 pages

Edition 1st Edition

Languages

PowerShell

Tools

Linux

Concepts

System Administration

Author (1):

Nick Parlow

View More author details

Table of Contents (23) Chapters

Preface

1. Part 1: PowerShell Fundamentals

2. Chapter 1: Introduction to PowerShell 7 – What It Is and How to Get It FREE CHAPTER

3. Chapter 2: Exploring PowerShell Cmdlets and Syntax

4. Chapter 3: The PowerShell Pipeline – How to String Cmdlets Together

5. Chapter 4: PowerShell Variables and Data Structures

6. Chapter 5: PowerShell Control Flow – Conditionals and Loops

7. Chapter 6: PowerShell and Files – Reading, Writing, and Manipulating Data

8. Chapter 7: PowerShell and the Web – HTTP, REST, and JSON

9. Part 2: Scripting and Toolmaking

10. Chapter 8: Writing Our First Script – Turning Simple Cmdlets into Reusable Code

11. Chapter 9: Don’t Repeat Yourself – Functions and Scriptblocks

12. Chapter 10: Error Handling – Oh No! It’s Gone Wrong!

13. Chapter 11: Creating Our First Module

14. Chapter 12: Securing PowerShell

15. Part 3: Using PowerShell

16. Chapter 13: Working with PowerShell 7 and Windows

17. Chapter 14: PowerShell 7 for Linux and macOS

18. Chapter 15: PowerShell 7 and the Raspberry Pi

19. Chapter 16: Working with PowerShell and .NET

20. Answers to Activities and Exercises

21. Index

Why subscribe?

22. Other Books You May Enjoy

How the pipeline works – parameter binding

The main difference between the output of PowerShell cmdlets and more generic shells is that instead of being file-like, the output is an object, with a type, properties, and methods. So, how does an object produced by one cmdlet get passed to another cmdlet?

Cmdlets can only accept input via their parameters. There is no other way, so it follows that the output objects of one cmdlet must be fed to a parameter of the next cmdlet in the pipeline. Consider the following cmdlet pipeline:

Get-Process | Sort-Object -Property CPU

We can only see one parameter here, -property, and it’s being given an argument of CPU. So, what’s going on? Sort-Object is being given two parameters, but we can’t see one of them. This is called pipeline parameter binding.

PowerShell takes the output of the first cmdlet, Get-Process, and must do something with it, so it looks for a parameter on the second cmdlet that can accept the...