Our customers have certainly not been shy about their interest in multiple languages of Windows PowerShell Updatable Help, and we’re grateful to hear how much they would value localized Help. Our challenge is this: Updatable Help is a new feature for this release of Windows PowerShell,
I published the source code for the Cmdlet Help Editor on CodePlex here: http://cmdlethelpeditor.codeplex.com/ . Please feel free to contribute.
for more information on the Cmdlet Help Editor, please check out the following post: http://blogs.msdn.com/b/powershell/archive/2007/09/01/new-and-improved-cmdlet-help-editor-tool.aspx
Wassim Fayed [MSFT]
When you refer to Windows PowerShell help topics, such as in tools and blog posts, be sure to refer to the most recent version of the help topics. Few things are less helpful or more confusing than sending a reader to a topic that is missing a parameter or includes an example that doesn’t work.
Beginning today, there’s a new way to look at Windows PowerShell cmdlets.
You’re used to looking at them this way:
Or, perhaps, this way:
But would you like to look at them this way?
What if getting a list of the remoting cmdlets was as easy as clicking a category name?
Several Windows PowerShell online help fans have requested a list of all of the URLs of Windows PowerShell Core online help topics in the TechNet Library. I’m providing them here so that they’re available to everyone.
The file includes URLs for the current Windows PowerShell Core conceptual (“about”),
In Windows PowerShell 2.0, you can write help topics for functions, scripts, and modules, just as you do for cmdlets and providers. In fact, as a best practice, you should always include help topics for all shared PowerShell items.
And we make it easy.
A new feature of Windows PowerShell 2.0 lets you write custom cmdlet help for Windows PowerShell providers. This blog explains how to do it. (The topic will also be covered in excruciating detail in MSDN, but we don’t want you to wait.)
ISE has an F1 help feature, where if you press F1 when your caret is over a cmdlet name, context sensitive help opens.
Shay Levy has a nice post on F1 help in the ISE herehttp://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/01/31/using-help-in-powershell-ise.aspxHe adds “I wanted to mimic the way ISE’s help works when you press F1 and allow an alias to be expanded to cmdlet name.” and he did it with calling hh.exe on the link
There is an alternative way;
(or How to Define the Help File Name in a Custom Windows PowerShell Snap-in)
We’ve discovered an error in our instructions for creating a custom Windows PowerShell snap-in. This error prevents Get-Help from finding the help files for cmdlets in the snap-in.