Basic Debugging in SAPIEN PowerShell Studio 2015

I wanted to share a little debugging trick with SAPIEN PowerShell Studio 2015. Logic bugs are not a fun. Essentially, your script is doing exactly what you told it to do, but it is not what you wanted it to do. Most likely, the contents of memory are not what you expected. SAPIEN PowerShell Studio 2015 has both a Variable and a Watch window to help you in your debugging efforts. Take a look at this code:

There is nothing wrong with it. I just want to use very basic code. By pressing Ctrl – F5 you will run this code normally. Pressing F5 runs the code in Debug Mode. In Debug Mode, nothing special happens. You have to set a break point.

Above, I clicked on line 16 and pressed F9. This is where execution of the code will stop and allow you to examine the contents of memory. Press F5 to see what happens next.

You can see the arrow beside line 16. This is where we currently are suspending execution. The Variables window is opened and I scrolled to the bottom of the list to see our variables. Variable Z is not in memory since we stopped execution on its line. While scrolling through this list, you may notice that all data in memory is being displayed. If you want to focus on a specific variable and ignore the rest, use the watch window. Right click X and select Add to Watch. Now click on the Watch tab.

Each time you run this code, this variable will be in the watch window until you remove it.

By pressing F5 again, you will resume script execution.

Comments

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix. This customization deals with Group Policy and PowerShell. For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material. I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO. This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy. One organization in the crowd had over 5,000 Group Policies. In an environment like that, the comment section can be priceless. I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers. The first command creates a collection with 2 duplicates of both 1 and 2. The second command creates another collection with the duplicates filtered out. The Compare-Object cmdlet will first find items that are diffe

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.

Jason Yoder, MCT

Search This Blog