Inspiration and sources

[MariusStorhaug]

Any interaction is a failure of automation. -Elon Musk

• Module management on a system:

  • https://github.com/JustinGrote/ModuleFast

• Link collections:

  • Awsome-Powershell

• Professional modules

  • https://github.com/PSAppDeployToolkit/PSAppDeployToolkit
  • PowerShell Module Browser | Microsoft Learn
  • Azure PowerShell
    • Docs | Microsoft Learn
    • PS Repo | GitHub
    • CLI Repo | GitHub
  • Microsoft Graph PowerShell
    • Docs | Microsoft Learn
    • PS Repo | GitHub
    • CLI Repo | GitHub

• Module Templating and frameworking

  • gaelcolas/Sampler | GitHub - Inspiration on bits and pieces that should be included in a generic PowerShell module repo, and best practices to follow (even though not all are followed here).
  • https://github.com/devblackops/Stucco
  • psake, A build automation tool written in PowerShell | GitHub
  • FriedrichWeinmann | GitHub
  • PowershellFrameworkCollective | GitHub
  • James Brundage | GitHub
  • PoshCode | GitHub

• PoshCode Actions | GitHub - Did not know this existed untill i started making my own. Approaches are different however.

• PoshCode ModuleBuilder | GitHub
  Evotec | GitHub

• http://ramblingcookiemonster.github.io/

• https://github.com/RamblingCookieMonster/

• <code.golf>

PowerShell Docs
PowerShell: Scripting
Powershell Team Blog

Inspiration to this page can come from

https://github.com/Microsoft/.github
https://github.com/GitHub/.github
https://github.com/PowerShell/.github
https://github.com/Azure/.github
https://github.com/spotify/.github
https://github.com/sap/.github
https://github.com/actions/.github
https://github.com/PowerShell/whatsnew

Should be built to support:
PSResourceGet | GitHub
PSResourceGet | Microsoft Learn

Top 50 modules

Define quality:

• https://github.com/PowerShell/DscResources/blob/master/HighQualityModuleGuidelines.md#creating-a-high-quality-dsc-resource-module

Module manifest:

• https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_module_manifests?view=powershell-7.3
• https://learn.microsoft.com/en-us/powershell/scripting/developer/module/how-to-write-a-powershell-module-manifest?view=powershell-7.3
• https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/new-modulemanifest?view=powershell-7.3
• https://learn.microsoft.com/en-us/powershell/gallery/concepts/package-manifest-affecting-ui?view=powershellget-2.x#powershell-gallery-feature-elements-controlled-by-the-module-manifest

PowerBI report:
https://msit.powerbi.com/view?r=eyJrIjoiM2E3MDllNDMtNGE4OS00NjdkLWI1ODEtZGI2MGNiYjA1ZmI1IiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9&pageName=ReportSection

Best practice:

• Suppressing output
  • $null =
• Array addition
  • [System.Collections.Generic.List[object]]::new() and then $list.Add($item)
  • [System.Collections.ArrayList]::new() and then $list.Add($item)
• String addition
  • Use -join operator not +=
• Processing large files

      try {
          $stream = [System.IO.StreamReader]::new($path)
          while ($line = $stream.ReadLine()) {
              if ($line.Length -gt 10) {
                  $line
              }
          }
      } finally {
          $stream.Dispose()
      }

  Instead of Get-Content $path | Where-Object { $_.Length -gt 10 }
• Looking up entries by property in large collections
  • Lookup using hash tables and keys to get items, instead of using where-object.
• Avoid Write-Host
  • Use Write-Output instead, or Write-Verbose for pipeline logs.
• Avoid repeated calls to a function
  • Move the loop into the function instead (call it only once).
• Avoid calling functions that support append, with append.
  • Instead gather all things that must be set, and then call the function once to set them all.
• Dont use * in ...ToExport properties for a module manifest.
  • Instead use explicit names. Best approach is to use a build step to generate the list of functions, cmdlets, variables and aliases to export.
  • If nothing is defined, then the default should be to export an empty array (@()).
• Avoid CDXML
  • Use other types of modules instead. In the order listed below:
    • Binary modules
    • Script/Manifest modules
    • CDXML modules
• Security
  • Preventing script injection attacks
    • Restruct the use of Invoke-Expression.
    • Use strongly typed parameters, and validate input. Think that all input can mask a command.
    • Wrap strings in single quotes, and use the -f operator to insert variables.
    • Use the EscapeSingleQuotedStringContent() method
  • Detecting vulnerable code with Injection Hunter