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

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