donderdag 27 mei 2010 8:46
Kurt Roggen
PowerShell Modules versus Snapins
Module
A module is a package that contains Windows PowerShell commands, such as cmdlets, providers, functions, variables, and aliases.
People who write commands can use modules to organize their commands and share them with others. People who receive modules can add the commands in the modules to their Windows PowerShell sessions and use them just like the built-in commands.
Since PowerShell 2.0, porting cmdlets became easier through the use of modules.
Snapins
A Windows PowerShell snap-in is a Microsoft .NET Framework assembly that contains Windows PowerShell providers and/or cmdlets. Windows PowerShell includes a set of basic snap-ins, but you can extend the power and value of Windows PowerShell by adding snap-ins that contain providers and cmdlets that you create or get from others.
When you add a snap-in, the cmdlets and providers that it contains are immediately available for use in the current session, but the change affects only the current session.
Builtin Snapins
Windows PowerShell includes a set of Windows PowerShell snap-ins that contain the built-in providers and cmdlets.
Microsoft.PowerShell.Core
| Contains providers and cmdlets used to manage the basic features of Windows PowerShell.
It includes the FileSystem, Registry, Alias, Environment, Function, and Variable providers and basic cmdlets like Get-Help, Get-Command, and Get-History. |
| Microsoft.PowerShell.Host | Contains cmdlets used by the Windows PowerShell host, such as Start-Transcript and Stop-Transcript. |
| Microsoft.PowerShell.Management | Contains cmdlets such as Get-Service and Get-ChildItem that are used to manage Windows-based features. |
| Microsoft.PowerShell.Security | Contains cmdlets used to manage Windows PowerShell security, such as Get-Acl, Get-AuthenticodeSignature and ConvertTo-SecureString. |
| Microsoft.PowerShell.Utility | Contains cmdlets used to manipulate objects and data, such as Get-Member, Write-Host, and Format-List. |
Related reading: Managing Windows Server 2008 R2 using PowerShell
Filed under: WindowsServer2008R2, Powershell