Modules were introduced with the release of PowerShell version 2.0. Modules represented a significant step forward over snap-ins. Unlike snap-ins, modules do not have to be formally installed or registered for use with PowerShell.
It is most common to find a module that targets a specific system or focuses on a small set of related operations. For example, the Microsoft.PowerShell.LocalAccounts module contains commands for interacting with the local account database (users and groups).
A module may be binary, script, dynamic, or manifest:
- Binary module: This is written in a language, such as C# or VB.NET, and then compiled into a library (DLL)
- Script module: This is a collection of functions written in the PowerShell language. The commands typically reside in a script module file (PSM1)
- Dynamic module: This does not have files associated with it. This is created using the
New-Modulecommand. The following command creates a very simple dynamic module that adds theGet-Number...
