Skip to main content

How to See a Cmdlet’s Code

This last week I had the privilege of speaking at the PowerShell Summit Asia in Singapore.  After an 11 hour day of speaking, you better believe that I had a lot of attendees asking me questions over the following 2 days.  A really good one that stuck in my head involves how to see the code that was used to write a cmdlet.  Hey, I teach PowerShell so this is a good one.

PowerShell cmdlets are actually either a “cmdlet” or a “function”.

PS C:\> Get-Command -Name Get-Process, Get-SMBShare

CommandType     Name            Version    Source                                                                               
-----------     ----            -------    ------                                                                               
Cmdlet          Get-Process     3.1.0.0    Microsoft.PowerShell.Management                                                      
Function        Get-SmbShare    2.0.0.0    smbshare                                                                             


Cmdlets are actually created from C# while functions are created with PowerShell.  Since C# is compiled we cannot crack them open to see what makes them tick without some extra software.  However, you can very easily see the code from a function

PS C:\> Get-Command -Name Get-SMBShare | Select-Object -ExpandProperty ScriptBlock | Out-File -FilePath ##Someplace to put it "

Set the –FilePath to a txt or PS1 file so you can look at the code.


It is no secret that I advocate to practice of “never reinvent the wheel”.  In other words if you need to know how a function did something, just look at the code.  

Comments

karthik can i import those files to androis studio and make chages in that to see a new app?
Personally, I have never tried it. Go ahead and let us know how it goes.

Popular posts from this blog

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.