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 list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the