Grammatical error:

[jbirley]

Chapter 9

Section: 9.1 Benefits of a monolithic PSM1

States

• Remember, in many cases, you can simple rename a .ps1 script into a script module .psm1 file and boom, you have a module. Next, add a module manifest so you can can assign the module version, define any dependencies, and set other types of metadata.

Recommendation

• Remember, in many cases, you can simply rename a .ps1 script into a script module .psm1 file and boom, you have a module. Next, add a module manifest so you can assign the module version, define any dependencies, and set other types of metadata.

Section: 9.3 Creating a dot-sourced module

States

• We’re going to build this module out some more by creating the individual function files.

Recommendation

• We’re going to further expand on this module by creating the individual function files.

Section: 9.3 Creating a dot-sourced module

States

• We just need them to output something so we can them working.

Recommendation

• We just need them to output something so we can see them working.

Section: 9.3 Creating a dot-sourced module

States

• `Get-AcmeEmployee will retrieve users from a simple, in-memory collection and supports optional filtering by the employee’s name.

Recommendation

• 'Get-AcmeEmployee' will retrieve users from a simple, in-memory collection and supports optional filtering by the employee’s name.

Section: 9.3 Creating a dot-sourced module (Creating flexible modules callout)

States

• The answer is we designing this module to be flexible and work in both the dot-sourced and monolithic PSM1 scenarios.

Recommendation

• The answer is we are designing this module to be flexible and work in both the dot-sourced and monolithic PSM1 scenarios.

Section: 9.3 Creating a dot-sourced module

States

• New-AcmeEmployee -Name 'Brandon Olin' -Title 'Site Reliability Engineer' -Verbose
• New-AcmeEmployee -Name 'Brandon Olin' -Title 'Author' -Verbose

Recommendation

• Code listing and code sample are not the same.

Section: 9.3 Creating a dot-sourced module

States

• That is a perfectly fine choice to make, but if you do, in the next section, we’ll add some automation to build the monolithic PSM1 from these source files.

Recommendation

• That is a perfectly fine choice to make. But if you do decide to build the monlithic PSM1, we’ll add some automation in the next section to make that easier.

Section: 9.4 Building a module - E pluribus enum (out of many, one)

States

• We aren’t producing a binary file full of machine-readable code by passing all of our .ps1 files into a compiler tool like gcc like you would if we were writing a program in C.

Recommendation

• We aren’t producing a binary file full of machine-readable code by passing all of our .ps1 files into a compiler tool like gcc as you would if we were writing a program in C.

Section: 9.4 Building a module - E pluribus enum (out of many, one)

States

• In our usage of the word, we’re taking PowerShell code from many sources (our .ps1) files, and concatenating them into a single output artifact, our PSM1 file.

Recommendation

• In our usage of the word, we’re taking PowerShell code from many sources (our .ps1 files), and concatenating them into a single output artifact, our PSM1 file.

Section: 9.4.1 Creating a project directory

States

• If there is ever a task that needs to to be done, the build script should be the one that takes care of it.

Recommendation

• If there is ever a task that needs to be done, the build script should be the one that takes care of it.

Section: 9.4.2.1 Creating an output directory

States

• Now let’s walk through that this script does. First off, it’s using the [CmdletBinding()] attribute, as all scripts as functions should, so we get verbose, and debug output if we need it.

Recommendation

• Now let’s walk through what this script does. First off, it’s using the [CmdletBinding()] attribute, as all scripts and functions should, so we get verbose and debug output if we need it.

Section: 9.4.3 Running the build script

States

• The PSM1 is this case, is just all the individual script files concatenated together.

Recommendation

• The PSM1 in this case, is just all the individual script files concatenated together.

Section: 9.4.4 Exporting functions in the manifest

States

• There are all just jammed into the PSM1, and we haven’t told PowerShell what else to do so it exports all the functions.

Recommendation

• They are all just jammed into the PSM1, and we haven’t told PowerShell what else to do so it exports all the functions.

Section: 9.5 Summary

States

• You may choose to use a different layout strategy, but if you want to build the PSM1 from your source files. the principals shown here remain the same.

Recommendation

• You may choose to use a different layout strategy. But if you want to build the PSM1 from your source files, the principals shown here remain the same.

[jbirley]

Favorite chapter so far.... chock full of practical knowledge! In my opinion, it could stand alone as a PowerShell reference on the topic.

[devblackops]

Thanks Jim! I'm continually amazed at what basic spell check and Grammarly don't catch.

I'll see about making this chapter a standalone blog post.