{"id":82,"date":"2007-02-27T12:00:00","date_gmt":"2007-02-27T20:00:00","guid":{"rendered":"http:\/\/testblog.sapien.com\/index.php\/2007\/02\/27\/fast-furious-powershell-find-that-function\/"},"modified":"2007-02-27T12:00:00","modified_gmt":"2007-02-27T20:00:00","slug":"fast-furious-powershell-find-that-function","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2007\/02\/27\/fast-furious-powershell-find-that-function\/","title":{"rendered":"Fast & Furious PowerShell: Find that Function"},"content":{"rendered":"

Like my recent post<\/a> about the Alias provider.  There is also a Function provider. You can use basically the same techniques that I used to explore aliases.<\/p>\n

dir function:<\/font><\/p>\n

Gives you basic information.  I like this:<\/p>\n

dir function: | select name,definition |format-table -auto<\/font><\/p>\n

because I can see more of the definition.  Even better, for each function name I can do something like this:<\/p>\n

PS E:\\ > (dir function:edit-file).definition
param([string]$path) $editor = “notepad.exe”
if ($PscxTextEditorPreference -ne $null -and $PscxTextEditorPreference.Length -gt 0)
{
Get-Command $PscxTextEditorPreference 2>&1 | out-null
if ($?) {
$editor = $PscxTextEditorPreference
}
} <\/font><\/p>\n

& $editor $path<\/font> <\/p>\n

Unlike Alias, there is no Get-Function cmdlet, so this is an easy way to discover the code behind a given function. Finally, here is the uber-command to enumerate all functions and their definitions: <\/p>\n

PS E:\\ > foreach ($item in (dir function:)) { write-host -back yellow -fore Blue $item.name;$item.definition}<\/font> <\/p>\n

Isn’t this fun? <\/p>\n<\/p>\n

Technorati tags: PowerShell<\/a>, Scripting<\/a>, Functions<\/a>, Get-ChildItem<\/a>, Provider<\/p>\n

<\/a><\/div>\n

del.icio.us tags: PowerShell<\/a>, Scripting<\/a>, Functions<\/a>, Get-childitem<\/a>, Provider<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"

Like my recent post about the Alias provider. There is also a Function provider. You can use basically the same techniques that I used to explore aliases.<\/p>\n

dir function:<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[25],"tags":[],"class_list":["post-82","post","type-post","status-publish","format-standard","hentry","category-windows-powershell"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/82","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=82"}],"version-history":[{"count":0,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/82\/revisions"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=82"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=82"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=82"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}