Skip to main content

How do you call functions from different code?

PowerShell Allows you to call up functions that are stored in other scripts. A few things that you need to consider before you do this.

1 – Your calling script must always have access to the script that it is including in its code.

2 – Troubleshooting. You now must consider multiple scripts with looking into bugs.

3- It will be harder to read your script because you will have to open multiple scripts.

We are going to first look at the calling script.

  1. . d:\PowerShell\functionlib.ps1
  2. $Name = Read-Host "What is your name: "
  3. WriteName($Name)
  4. StaggerName($Name)

Line 1 is telling our script the file path to another script to include. In this case, . d:\PowerShell\FunctionLib.ps1.

Line 2 is asking for the user to input data.

Lines 3 and 4 call 2 different functions from the same external script.

Now let us look at the external script being called.

  1. Function WriteName($strName)
  2. {
  3. Write-Host $Name
  4. }

  1. Function StaggerName($strName)
  2. {
  3. $RevName = ""
  4. For($i=0; $i -le $strName.length-1; $i++)
  5. {
    1. $RevName = $strName.Remove($i)
    2. $RevName
  6. }
  7. }

There are two functions listed here, WriteName and StaggerName. We are also sending data to each of these functions.

This can be advantageous so you do not need to rewrite code or do a Copy-Paste between source files. Just remember if that code is being used by multiple scripts before you modify it.

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