Skip to main content

What Order do you need to list Functions?

I am actually correcting myself on this one.  I’m at 35,000 feet right now enjoying a ride in the flying tin can while looking over my notes from this past weeks Advanced PowerShell class in Fort Wayne.  One of the questions that came up is the order that you need to list functions.  I gave a bad answer. 
I had always been taught to declare a function before I call it.  It makes sense.  How do you know how to execute instructions before you are told what the instructions are?  Take a look at this code:

Function Show-A
{
    Write-Host "Function A" -ForegroundColor Green
}

Function Show-B
{
    Write-Host "Function B" -ForegroundColor Cyan
    Show-A
}

Show-B

Here I am declaring function Show-A before it is called by function Show-B.  Here is the result:
Function B
Function A

Here is my surprise.  I changed the code an placed Function Show-B1 before Function Show-A1.  I then called Function Show-B1 and it all worked.

Function Show-B1
{
    Write-Host "Function B" -ForegroundColor Cyan
    Show-A1
}
Function Show-A1
{
    Write-Host "Function A" -ForegroundColor Green
}


Show-B1

Function B
Function A

Next I insert the calling statement for function Show-B2 before Function Show-A2 is called.  In other words, I am running Show-B2 before Show-A2 is read.  It still works.

Function Show-B2
{
    Write-Host "Function B" -ForegroundColor Cyan
    Show-A2
}

Show-B2
Function Show-A2
{
    Write-Host "Function A" -ForegroundColor Green
}


Function B
Function A

One rule that I could not break is the rule on calling a variable before you declare its value.
Function Show-B2
{
    Write-Host "Function B" -ForegroundColor Cyan
    Show-A2
    Write-Host $String
}
Function Show-A2
{
    Write-Host "Function A" -ForegroundColor Green
}


Show-B2
$String = "Hello"

Here Show-B2 is attempting to write the value of $String.  The problem is, $String is not assigned until after Show-B2 is executed.  The value of $String is NULL and is not displayed.
Function B
Function A

So, I stand corrected.  I uploaded this post to the online class files that I created for this class so I could correct my error.

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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...

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.