PowerGUI works great with cmdlets from Microsoft, VMware, Quest and other vendors, but what if it does not seem to “see” the ones which you created on your own?
Fear not, the issue is most likely very straight-forward and easy to resolve. Most likely you either don’t have the your PowerShell snapin selected in PowerGUI’s File/PowerShell Libraries, or you forgot to supply a help file for your cmdlets.
So here are the steps to take to make sure your cmdlets show up in PowerGUI admin console and editor as first-class citizens:
1. Make sure your cmdlets have help (creating a help file in PowerShell is very straight-forward with this utility). To check that the help is working open a PowerShell prompt and type:
Get-Help your_cmdlet_name
2. Make sure PowerGUI is using your cmdlets by going to the File/PowerShell Libraries and selecting your PowerShell snapin.
That’s it. Now if you add a node in the PowerGUI admin console all your get-* cmdlets should be there. In the editor, your cmdlets should get tooltips, intellisense, and F1 help. Your snapin is now as good as everybody’s else! 
Tags: Extensibility, PowerGUI, PowerPack, cmdlets
Subscribe by email
This is a more recent posting from Microsoft:
http://blogs.msdn.com/powershell/archive/2007/09/01/new-and-improved-cmdlet-help-editor-tool.aspx
Although, I think both posts point to the same downloadable file.
Marco
Thanks Marco! I’ve updated the post so it references the more recent help-tool description.