Comments on: Expanding Wildcards in PowerShell http://www.owenpellegrin.com/blog/powershell/expanding-wildcards-in-powershell/ I write stuff here Mon, 30 Jan 2012 02:39:32 +0000 hourly 1 http://wordpress.org/?v=3.1.4 By: Powershell wildcards | Hyfresh http://www.owenpellegrin.com/blog/powershell/expanding-wildcards-in-powershell/comment-page-1/#comment-32252 Powershell wildcards | Hyfresh Fri, 04 Nov 2011 09:07:30 +0000 http://www.atmaweapon.org/blog/?p=29#comment-32252 [...] Expanding Wildcards in PowerShell | Yeah it’s a blogExpanding Wildcards in PowerShell. Posted on July 22, 2008 by Owen Pellegrin. Yesterday I thought I’d jump into the deep end of PowerShell and try to make a … [...] [...] Expanding Wildcards in PowerShell | Yeah it’s a blogExpanding Wildcards in PowerShell. Posted on July 22, 2008 by Owen Pellegrin. Yesterday I thought I’d jump into the deep end of PowerShell and try to make a … [...]

]]> By: SteveSw http://www.owenpellegrin.com/blog/powershell/expanding-wildcards-in-powershell/comment-page-1/#comment-21241 SteveSw Sun, 29 May 2011 20:15:41 +0000 http://www.atmaweapon.org/blog/?p=29#comment-21241 I came across this several years after the fact, trying to figure out how to expand a parameter passed to a function with wild cards in it. This code seems to work: passed a single string $pattern, it will fill a character array $files with all the files that match the pattern in the current directory: function expand-arg { [CmdletBinding()] param([string] $pattern) $loc = Get-Location $provider = $loc.Provider $files = @() $longfiles = $pscmdlet.GetResolvedProviderPathFromPSPath($pattern, [ref] $provider) $longfiles | % { $file = gci $_ ; $files += $file.Name } # your logic here } There are several things here that weren't entirely obvious to me. First, I used the CmdletBinding() attribute so that I could get at a pscmdlet instance (which implements the GetResolvedProviderPathFromPSPath() method). Second, I fished a ProviderInfo instance out of the current location (this should work inside any provider) -- you need one of those to pass as the second argument of GetResolvedProviderPathFromPSPath()). And then third, I used gci to strip the filename off the complete names returned to me by GetResolvedProviderPathFromPSPath(), and to discard the current directory (which is inexplicably returned by GetResolvedProviderPathFromPSPath() even when it doesn't match the wildcards in the pattern). I came across this several years after the fact, trying to figure out how to expand a parameter passed to a function with wild cards in it.

This code seems to work: passed a single string $pattern, it will fill a character array $files with all the files that match the pattern in the current directory:

function expand-arg
{
[CmdletBinding()]
param([string] $pattern)
$loc = Get-Location
$provider = $loc.Provider
$files = @()
$longfiles = $pscmdlet.GetResolvedProviderPathFromPSPath($pattern, [ref] $provider)
$longfiles | % { $file = gci $_ ; $files += $file.Name }

# your logic here
}

There are several things here that weren’t entirely obvious to me. First, I used the CmdletBinding() attribute so that I could get at a pscmdlet instance (which implements the GetResolvedProviderPathFromPSPath() method). Second, I fished a ProviderInfo instance out of the current location (this should work inside any provider) — you need one of those to pass as the second argument of GetResolvedProviderPathFromPSPath()). And then third, I used gci to strip the filename off the complete names returned to me by GetResolvedProviderPathFromPSPath(), and to discard the current directory (which is inexplicably returned by GetResolvedProviderPathFromPSPath() even when it doesn’t match the wildcards in the pattern).

]]>