I built this site primarily for my own use. When I first started learning Powershell, I’d go through a help file and find references to other commands, providers, or about files and kind of go down a rabbit hole. Then, I’d think, “I know that at the bottom of the help text it says ‘Related Topics’ but that doesn’t seem all inclusive. What if I want to know all the cmdlets that use a credential parameter?

There’s no way to do that.

Also, Microsoft’s website merely republishes the command prompt help text or gives you 4.0 help for 2.0 items. Powershell 2.0 is what comes with Windows 7 and Windows Server 2008 R2 and if you’re like me you can’t count on any of your machines having newer Powershell versions installed.

I actually used a Powershell script to create this site. Posts are categorized by type (cmdlets, Providers, and HelpFiles). Cmdlets are also categorized by Verb and Noun. So if you wanted to know all the Get-xxxx cmdlets, you’d look at the Get category. If you wanted to know about all the xxxx-Member cmdlets, you’d look at the Member category.

If another cmdlet, provider, or helpfile is mentioned in a post, it is linked. That way if you’re reading through Set-Alias and get to where it talks about Format-Table, you can click on over without much effort.

Categories are listed in the sidebar, or if you’d like you can just type the category in the address bar at the end of http://adamringenberg.com/powershell2/category/[Category Name].

Posts are also tagged with the parameters they use. The Set-Alias cmdlet, for example, has this syntax:
Set-Alias [-Name] [-Value] [-Description ] [-Force] [-Option {None | ReadOnly | Constant | Private | AllScope}] [-PassThru] [-Scope ] [-Confirm] [-WhatIf] []

Accordingly, it is tagged with CONFIRM, DEBUG, DESCRIPTION, ERRORACTION, ERRORVARIABLE, FORCE, NAME, OPTION, OUTBUFFER, OUTVARIABLE, PASSTHRU, SCOPE, VALUE, VERBOSE, WARNINGACTION, WARNINGVARIABLE, and WHATIF.

In the post, those parameters are italicized for easy identification.

I hope you enjoy the site.