PowerShell v3 in a Year Day 10 about Core Commands

PowerShell introduced the concept of providers as a way to try and flatten access to data stores. Windows has access to a wide array of data stores, and, typically, each type of data store comes with its on technology, techniques, API and gotchas. In short, dealing with data, pre-PowerShell, could be very frustrating. Who had the time to keep all of the syntax quirks, warts and whatnot about each technology straight all the time, not to mention version changes, upgrades, patches, etc, etc, etc. To get around this the PowerShell team created providers as a mechanism to give common language, syntax, and, feel for the various data store technologies.

Within each provider there are common cmdlets that can be used to navigate, manipulate and otherwise, manage the data stores. Below is a list of cmdlets designed for use with providers. There is not a lot of interpretation required with this list. Although I am merely listing these here, I will, eventually, cover all of the cmdlets in the course of work through the rest of the "year".

• ChildItem cmdlets
• Get-ChildItem
• Content cmdlets
• Add-Content
• Clear-Content
• Get-Content
• Set-Content
• Item cmdlets
• Clear-Item
• Copy-Item
• Get-Item
• Invoke-Item
• Move-Item
• New-Item
• Remove-Item
• Rename-Item
• Set-Item
• ItemProperty cmdlets
• Clear-ItemProperty
• Copy-ItemProperty
• Get-ItemProperty
• Move-ItemProperty
• New-ItemProperty
• Remove-ItemProperty
• Rename-ItemProperty
• Set-ItemProperty
• Location cmdlets
• Get-Location
• Pop-Location
• Push-Location
• Set-Location
• Path cmdlets
• Join-Path
• Convert-Path
• Split-Path
• Resolve-Path
• Test-Path
• PSDrive cmdlets
• Get-PSDrive
• New-PSDrive
• Remove-PSDrive
• PSProvider cmdlets
• Get-PSProvider

Related Post: