[PSCX] What happened to Get-CmdLetMaml

I've been backreading this froup, and i see a couple of references to Get-CmdLetMaml in PowershellCX, but it does not seem to be in the latest release.

I can see it's been removed, is there a replacement?

Joris

Have a look at get-pssnapinhelp
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Joris van Lier" wrote:

> I've been backreading this froup, and i see a couple of references to Get-CmdLetMaml in PowershellCX, but it does not seem to be in the latest release.
>
> I can see it's been removed, is there a replacement?
>
> Joris
>

"RichS" <RichS@discussions.microsoft.com> wrote in message
news:3742F9D0-244A-4FB6-B3D4-858AC271D562@microsoft.com...
> Have a look at get-pssnapinhelp
> --

Get-PSSnapinHelp requires access to partial help files in order to generate
output. In this area I think we took a step backwards in 1.1 but our
ultimate goal is to provide a mechanism that allows for help localization.
There was no good way to get there with the old cmdlet (Get-CmdletMaml) and
our new approach isn't anywhere near as streamlined as I would like it to
be. Anyway I've include a zip of the help generation scripts and XSLTs that
we used in PSCX 1.1 to generate the Pscx.dll-help.xml file.

The way to use this stuff is:

1. Modify the last line New-HelpSkeleton.ps1 to specify your snapin name and
run the script. Specify something like .\Help (make sure there is a Help
folder created) as the parameter. A template file for each cmdlet will be
generated in this Help dir.
2. Fill in the description, detailed description and so in the template
files.
3. Now run GeneratePscxHelpXml.ps1 - again you will need to modify line 33
to substitute the name of your cmdlet.

Sorry about the roughness of this all. We will make this better (ie a
reusable piece of what PSCX delivers) for the next release.

--
Keith