Skip to main content

Scope issue with Windows PowerShell ISE

By

Although I like the Windows PowerShell ISE, I came across a problem related to scope.  For many months, I’ve been fighting issues of elements in my scripts not clearing out between runs.  What I have come to find out is that when you run a  script in the ISE and the script completes, its scope is not destroyed.  Here is an example.

 

image

 

In the above example, in the shell, I set a variable to the value of 100.  Since this is done in the shell, this variable is stored in the global scope.  By executing Get-Variable, I can see the value of a is 100.

 

image

Now let’s do the same thing in the ISE.

image

 

If I run Get-Variable in the ISE, I receive this:

image

 

So far, all is as expected.  Now let’s execute a script in the ISE that changes the value of $a to 500 and then displays it:

image

image

 

Now let’s run Get-Variable again inside the ISE.

image

 

The Value of $a is still 500.  I suspect this behavior is what has caused me a lot of head aches over the past few months.  I now program with the ISE, but test in the shell by Dot Sourcing the function into the shell.  When using the Shell, the Script scope is destroyed and you start with a blank slate each time you run your function.

Labels

Labels:

Comments

Jeffery Hicks said…
You've discovered the reason I tell students to NOT use the ISE to run production scripts. The ISE maintains a global scope which comes in handy when developing a script. But can wreak havoc otherwise.
August 1, 2011 at 4:02 AM
Jason Yoder, MCT said…
Jeff, I love your PowerBall script. I wrote something like that on my Apples IIe many years ago.
August 1, 2011 at 5:28 AM
Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more