Skip to main content

How to enable Get-Help with your functions in PowerShell

PowerShell has a very robust online help capabilities.  These abilities are extended to you, the user, when you are creating functions and scripts.  You may have functions that you load as part of your profile or that you have created as part of a customized module.  To do this is very simple.  Take a look at the function below.
Function WriteText {
Param (
    [parameter(Mandatory=$True,ValueFromPipeline=$True)]$InputValue `
    = (Read-Host 'Please provide an input value: '))
BEGIN {}
PROCESS{
    Write-Host $InputValue
    }
END {}
}

This function simply outputs what you put into it.  Let’s add some help functionality to it. 

To do this, we need to add a block comment section immediately after the Function declaration line.  Block comments are normal comment statements.  The difference is that instead of every line starting with ‘#’, we start with ‘<#’.  You can type as many lines as you want and all of them will be considered comments until you end the comment block with ‘#>’.

We add the help by adding these lines.
.SYNOPSIS
Provides a brief statement of what this function or script does.
.DESCRIPTION
This is a more detailed explaination of the script or function.
.PARAMETER parameter
This will descript the purpose of each parameter.  Add addition .PARAMTER lines for multiple parameters
.EXAMPLE
Provide one or more examples by adding more .EXAMPLE lines.
.INPUTS
This is the list of Microsoft .NET Framework objects that can be piped to this function.
.OUTPUTS
The .NET Framework type of object that is returned from this function or cmdlet.
.NOTES
Any additional information about this function or cmdlet.

You can read about these, and more attributes of the help file by executing this line in PowerShell: help About_ comment_based_help

Let’s add a help file and see the results.

Function WriteText {
<#
.SYNOPSIS
Writes what you give it.
.DESCRIPTION
This function displays the input that it was provided.
.PARAMETER $InputValue
Accepts String or integer values.
.EXAMPLE
WriteText "Hello World"
.EXAMPLE
WriteText -InputValue "Hello World"
#>
Param (
    [parameter(Mandatory=$True,ValueFromPipeline=$True)]$InputValue `
    = (Read-Host 'Please provide an input value: '))
BEGIN {}
PROCESS{

    Write-Host $InputValue
    }
END {}
}

Here is the help file if we execute Get-Help WriteText –Full
NAME
    WriteText
   
SYNOPSIS
    Writes what you give it.
   
SYNTAX
    WriteText [-InputValue] <Object> [<CommonParameters>]
   
   
DESCRIPTION
    This function displays the input that it was provided.
   

PARAMETERS
    -InputValue <Object>
       
        Required?                    true
        Position?                    1
        Default value               
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters? 
       
    <CommonParameters>
        This cmdlet supports the common parameters: Verbose, Debug,
        ErrorAction, ErrorVariable, WarningAction, WarningVariable,
        OutBuffer and OutVariable. For more information, type,
        "get-help about_commonparameters".
   
INPUTS
   
OUTPUTS
   
    -------------------------- EXAMPLE 1 --------------------------
   
    C:\PS>WriteText "Hello World"

   -------------------------- EXAMPLE 2 --------------------------
   
    C:\PS>WriteText -InputValue "Hello World"

  
RELATED LINKS

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...