Can we see the source code for PowerShell cmdlets?

Question

I'm learning some PowerShell. Is it possible to see the source code for a built-in cmdlet like Get-ChildItem ?

Answer 1

The source for Powershell is now available on Github.
The source for Get-ChildItem can be found here .

Answer 2

Actually, your best bet is to go check out PowerShell Community Extensions . This open source software community project is "aimed at providing a widely useful set of additional cmdlets...". The developers on the project are PowerShell MVPs and know their stuff.

As far as using reflection on the existing PowerShell cmdlets, PowerShell MVP Oisin Grehan made a handy function titled " Reflect-Cmdlet ". I won't steal his code and place it here, but basically what you do is:

Get-Command Get-ChildItem | Reflect-Cmdlet

And then .NET Reflector pops up with the right assembly opened up and expanded and everything. It's really pretty cool.

Answer 3

For compiled Cmdlets, you can get the path to the .dll with:

(Get-Command Get-ChildItem).DLL

(Replace Get-ChildItem with the cmdlet you are interested in)

Example:

PS C:\Windows\system32> (Get-Command Get-StoragePool).DLL

PS C:\Windows\system32> 

Once you know the path to the .dll , you can open it with a .NET disassembler like dotPeek :

& dotPeek64.exe (Get-Command Get-ChildItem).DLL

Answer 4

I think if you were just starting PowerShell, this is what you'd be looking for:

$metadata = New-Object system.management.automation.commandmetadata (Get-Command Get-Process)
[System.management.automation.proxycommand]::Create($MetaData) | out-file C:\powershell\get-process.ps1

This will create a script which shows how Get-Process runs. Put in any cmdlet you want to replace Get-Process. If you want to google more about it, this is how you would create a proxy function.

Answer 5

You might also like to take a look at Windows Installer PowerShell Snap-In on CodePlex. It's a smaller project than the community extensions, so it is easier to get your head around what's going on.

Check out Professional Windows PowerShell Programming: Snapins, Cmdlets, Hosts and Providers (Wrox Professional Guides), ISBN: 0470173939 - it's one of the most useful books I've found for writing cmdlets and providers.

Answer 6

You should be able to use .NET Reflector to "see" the source code. You need to know the assembly though, but it should also accessible using the GetType method or similar.

This PowerShellLanguage .NET Reflector Add-In can perhaps be useful.

Answer 7

PowerShell cmdlets' assemblies are located in GAC. You can find "Get-ChildItem" cmdlet in:

Microsoft.PowerShell.Commands.Management assembly, Microsoft.PowerShell.Commands.GetChildItemCommand class.

I've used ILSpy .NET decompiler and filtered GAC assemblies by "powershell" string. As I understand, Microsoft.PowerShell.Commands.* assemblies contain built-in cmdlets.

Answer 8

我不相信 PowerShell 的源代码曾经发布过。

Answer 9

Some code can be found on the Reference Resource Site: http://referencesource.microsoft.com/#System.Management.Automation/System/Management/Automation/ChildItemCmdletProviderIntrinsics.cs,c6eed9f6a5417c19

This only gives the outline though; not the code's detail.

Answer 10

For some cmdlets that are installed with Install-Module and contain source code and not binaries, (eg PSnmap):

Install-Module -Name PSnmap

...you can view their code by looking at the Definition property from:

Get-Command Invoke-PSnmap | Format-List

If not, most likely, you will need to decompile some binary (eg the file specified in the DLL property).