{"id":5711,"date":"2008-07-17T19:03:00","date_gmt":"2008-07-17T19:03:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2008\/07\/17\/dude-wheres-my-manual\/"},"modified":"2019-02-18T13:13:06","modified_gmt":"2019-02-18T20:13:06","slug":"dude-wheres-my-manual","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/dude-wheres-my-manual\/","title":{"rendered":"Dude, Where's My Manual?"},"content":{"rendered":"

<\/p>\n

Windows PowerShell comes with a lot of help files and documents, but, somehow, my favorite and most-frequently-used help is the help that  I get by typing “Get-Help” in the console.<\/span><\/p>\n

 <\/span><\/p>\n

And I have always wondered why this help is not readily available as a  single document, ready to be viewed, searched, and printed. Well, now it is, with this simple Get-Manual script. <\/span><\/p>\n

 <\/span><\/p>\n

This script merges all of the about_* help content with cmdlet help, and puts it into one pretty formatted Microsoft Word document (.doc). Once you have this document, you can search it for specific content. Or, you can print it and have some enjoyable reading while sitting in your favorite armchair by the fireplace during the long winter evenings \ud83d\ude42<\/span><\/p>\n

 <\/span><\/p>\n

Updated 09\/30\/2008<\/strong>: Now the script not only collects the about_*.txt files, but it also includes the content of cmdlet help. It is also more localization-friendly. (Thanks to Markus for his brilliant CDATA suggestion!) <\/span><\/p>\n

<\/font><\/font><\/span> <\/font><\/span><\/p>\n

———————————————————————<\/span><\/p>\n

 <\/span><\/p>\n

# Get-Manual.ps1<\/span><\/p>\n

# This script merges the text from all about* files
# in the Windows PowerShell installation directory ($pshome)
# and help content from cmdlet help
# into one MS Word document file and opens the file that was created.<\/span><\/p>\n

# Setting up helper functions.<\/span><\/p>\n

function MakeHeading($text)
{
 return ‘<w:p><w:pPr><w:pStyle w:val=”Heading1″ \/><\/w:pPr><w:r><w:t><![CDATA[‘ + $text + ‘]]><\/w:t><\/w:r><\/w:p>’
}<\/span><\/p>\n

function MakeParagraph($text)
{
 return ‘<w:p><w:r><w:t><![CDATA[‘ + $text + ‘]]><\/w:t><\/w:r><\/w:p>’
}<\/span><\/p>\n

<\/p>\n

# Set the file name for generated WordML document.
$doc = “PowerShell Get-Help Content.doc”<\/p>\n

“Generating MS Word document…”<\/p>\n

$sb=new-object system.text.stringbuilder<\/p>\n

$null = $sb.Append(@’
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes” ?>
<?mso-application progid=”Word.Document”?>
<w:wordDocument
  xmlns:w=”http:\/\/schemas.microsoft.com\/office\/word\/2003\/wordml<\/a>“
  xmlns:wx=”http:\/\/schemas.microsoft.com\/office\/word\/2003\/auxHint<\/a>“
 w:macrosPresent=”no” w:embeddedObjPresent=”no” w:ocxPresent=”no” xml:space=”preserve”>
 <w:styles>
  <w:versionOfBuiltInStylenames w:val=”4″ \/>
  <w:style w:type=”paragraph” w:default=”on” w:styleId=”Normal”>
   <w:name w:val=”Normal” \/>
   <w:rPr>
    <w:rFonts w:ascii=”Lucida Console” w:h-ansi=”Lucida Console” w:cs=”Lucida Console” \/>
    <w:sz w:val=”24″ \/>
    <w:sz-cs w:val=”24″ \/>
    <w:lang w:val=”EN-US” w:fareast=”ZH-CN” w:bidi=”AR-SA” \/>
   <\/w:rPr>
  <\/w:style>
  <w:style w:type=”paragraph” w:styleId=”Heading1″>
   <w:name w:val=”heading 1″ \/>
   <wx:uiName wx:val=”Heading 1″ \/>
   <w:basedOn w:val=”Normal” \/>
   <w:next w:val=”Normal” \/>
   <w:pPr>
    <w:pStyle w:val=”Heading1″ \/>
    <w:keepNext \/>
    <w:spacing w:before=”240″ w:after=”120″ \/>
    <w:outlineLvl w:val=”0″ \/>
   <\/w:pPr>
   <w:rPr>
    <w:b \/>
    <w:b-cs \/>
    <w:kern w:val=”32″ \/>
    <w:sz w:val=”32″ \/>
    <w:sz-cs w:val=”32″ \/>
   <\/w:rPr>
  <\/w:style>
 <\/w:styles>
 <w:docPr>
  <w:view w:val=”web”\/>
  <w:zoom w:val=”full-page” w:percent=”100″\/>
 <\/w:docPr>
 <w:body>
‘@)<\/p>\n

# Get all content from about* help files.
$filter = “about*.txt”
dir $pshome -filter $filter -recurse | %{
 $null = $sb.Append((MakeHeading($_)))
 
 get-content $_.FullName | %{
  $null = $sb.Append((MakeParagraph($_)))
 }
}<\/p>\n

# Get all content from cmdlet help.
get-command | %{
 $null = $sb.Append((MakeHeading($_.Name + ‘ Cmdlet’)))<\/p>\n

 $helpText = $_ | get-help -full | Out-String<\/p>\n

 if ($helpText -eq “”) { $helpText= ‘<no help found>’ }<\/p>\n

 $helpText -split “`n” | %{
  $null = $sb.Append((MakeParagraph($_)))
 }
}<\/p>\n

$null = $sb.Append(“<\/w:body><\/w:wordDocument>”)<\/p>\n

# Write generated string to document file.
$sb.ToString() | out-file $doc -encoding UTF8<\/p>\n

# Open the resulting file in MS-Word.
$null = [System.Diagnostics.Process]::Start(“$pwd\\$doc”)<\/p>\n

“Done”
<\/span> <\/span><\/p>\n

——————————————————————————<\/span><\/p>\n

 <\/font><\/span><\/p>\n

Vladimir Averkin<\/font><\/font><\/span><\/p>\n

Windows PowerShell Test<\/font><\/font><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Windows PowerShell comes with a lot of help files and documents, but, somehow, my favorite and most-frequently-used help is the help that  I get by typing “Get-Help” in the console.   And I have always wondered why this help is not readily available as a  single document, ready to be viewed, searched, and printed. Well, […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5711","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":"

Windows PowerShell comes with a lot of help files and documents, but, somehow, my favorite and most-frequently-used help is the help that  I get by typing “Get-Help” in the console.   And I have always wondered why this help is not readily available as a  single document, ready to be viewed, searched, and printed. Well, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/5711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=5711"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/5711\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=5711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=5711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=5711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}