Has select-string changed behavior with RC2?

I have previously (some months ago, earlier PS build) used a command such as

get-content *.ps1 | select-string function -list | % { $_.path }

(trying to list all the files in current directory that have functions
defined in them).

This used to give me the filenames. Now all I get is output like this

InputStream
InputStream
InputStream
InputStream
InputStream

..... (one line for each file that select-string finds with a match)

select-string produces a stream of MatchInfo objects; but why does the path
field of the MatchInfo object not identify the filename? MatchInfo also has
a filename property; it behaves the same.

I see that I can achieve my goal directly with select-string thus:
select-string -path *.ps1 -list | % { $_.path }

which is fine for this simple case - but what if I need something more
complex earlier in the stream to identify the set of files to be searched?
For example, I want to find all such files in a directory tree and search
them:

get-childitem -path *.ps1 -recurse | get-content | select-string function
-list | % { $_.path }

I think you probably used "Get-Item" to start the pipeline.

Lee

"forestial" <forestial@discussions.microsoft.com> wrote in message
news3842C0C-0810-4065-8525-7411B44E0AE8@microsoft.com...
>I have previously (some months ago, earlier PS build) used a command such
>as
>
> get-content *.ps1 | select-string function -list | % { $_.path }
>
> (trying to list all the files in current directory that have functions
> defined in them).
>
> This used to give me the filenames. Now all I get is output like this
>
> InputStream
> InputStream
> InputStream
> InputStream
> InputStream
>
> .... (one line for each file that select-string finds with a match)
>
> select-string produces a stream of MatchInfo objects; but why does the
> path
> field of the MatchInfo object not identify the filename? MatchInfo also
> has
> a filename property; it behaves the same.
>
> I see that I can achieve my goal directly with select-string thus:
> select-string -path *.ps1 -list | % { $_.path }
>
> which is fine for this simple case - but what if I need something more
> complex earlier in the stream to identify the set of files to be searched?
> For example, I want to find all such files in a directory tree and search
> them:
>
> get-childitem -path *.ps1 -recurse | get-content | select-string function
> -list | % { $_.path }

Ouch! You are correct. My memory is bad, and my notes are worse.

"Lee Holmes [MSFT]" wrote:

> I think you probably used "Get-Item" to start the pipeline.
>
> Lee
>
>