1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
|
# List all loaded modules Get-Module # Available modules Get-Module -ListAvailable # Specific module Get-Module -ListAvailable -Name 'AppLocker*' # Import Get-Module -ListAvailable -Name 'AppLocker*' | Import-Module Import-Module 'AppLocker' # Remove Get-Module -ListAvailable -Name 'AppLocker*' | Remove-Module # List commands of a module Get-Command -Module 'AppLocker' # Get help of a specific command Get-Command -Module 'AppLocker' -Name 'Test-AppLockerPolicy' | Get-Help |
Script Modules
A script module is a file (.psm1) that contains any valid Windows PowerShell code. Script developers and administrators can use this type of module to create modules whose members include functions, variables, and more.
|
Import-Module '.\lib\module.psm1' -Force |
Binary Modules
A binary module is a .NET Framework assembly (.dll) that contains compiled code. Cmdlet developers can use this type of module to create modules that contain cmdlets, providers, and more. (Existing snap-ins can also be used as binary modules.)
Manifest Modules
A manifest module is a module that includes a manifest (described later in this section) to describe its components, but that does not specify a root module in the manifest. A module manifest does not specify a root module when the ModuleToProcess
key of the manifest is blank. In most cases, a manifest module also includes one or more nested modules using script modules or binary modules. A manifest module that does not include any nested modules can be used when you want a convenient way to load assemblies, types, or formats.
Dynamic Modules
A dynamic module is a module that does not persist to disk. This type of module enables a script to create a module on demand that does not need to be loaded or saved to persistent storage. By default, dynamic modules created with the New-Module cmdlet (described in the following sections) are intended to be short-lived and therefore cannot be accessed by the Get-Module cmdlet