Weird behavior using -Include switch on Get-ChildItem on local dir

I have two directories that are identical including file timestamps. One
directory is on a remote computer and the other directory is on my local pc.
When I get the directory listing and use the -Include filter, I get different
results:

Local machine:
------------------
Command: Get-ChildItem c:\mydir\ -Include *.wav
Result: No files returned

Remote machine:
--------------------
Command: Get-ChildItem \\remotemachine\mydir -Include *.wav
Result: Returns all the files that match the *.wav mask

Other than the path to the directory, these commands are identical. What I
don't understand is why the behavior is different from the remote machine to
the local machine.

To make matters more confusing, the following command works as expected on
the local machine:

Get-ChildItem *.wav

What is it that I don't understand about the -Include switch?

Thanks,

Don

It seems to work with -include on both local and remote machines if the path
specification ends mydir\*

This is sort of hinted at in the documentation where is says

The Include parameter is effective only when the command includes the
Recurse parameter or the path leads to the contents of a directory, such as
C:\Windows\*, where the wildcard character specifies the contents of the
C:\Windows directory.


--
Richard Siddaway

Please note that all scripts are supplied "as is" and with no warranty


"Don Dally" wrote:

> I have two directories that are identical including file timestamps. One
> directory is on a remote computer and the other directory is on my local pc.
> When I get the directory listing and use the -Include filter, I get different
> results:
>
> Local machine:
> ------------------
> Command: Get-ChildItem c:\mydir\ -Include *.wav
> Result: No files returned
>
> Remote machine:
> --------------------
> Command: Get-ChildItem \\remotemachine\mydir -Include *.wav
> Result: Returns all the files that match the *.wav mask
>
> Other than the path to the directory, these commands are identical. What I
> don't understand is why the behavior is different from the remote machine to
> the local machine.
>
> To make matters more confusing, the following command works as expected on
> the local machine:
>
> Get-ChildItem *.wav
>
> What is it that I don't understand about the -Include switch?
>
> Thanks,
>
> Don
>

Rich,

Thanks. I missed that in the documentation. The addition of the wildcard on
the parent object gave me the results I expected.

Now the only curiosity I have is why is the behavior inconsistent when
dealing with a remote directory?

Don


"RichS" <RichS@discussions.microsoft.com> wrote in message
news:36B45FB8-F789-4350-809D-2242FC4CCFA6@microsoft.com...
> It seems to work with -include on both local and remote machines if the
> path
> specification ends mydir\*
>
> This is sort of hinted at in the documentation where is says
>
> The Include parameter is effective only when the command includes the
> Recurse parameter or the path leads to the contents of a directory, such
> as
> C:\Windows\*, where the wildcard character specifies the contents of the
> C:\Windows directory.
>
>
> --
> Richard Siddaway
>
> Please note that all scripts are supplied "as is" and with no warranty
>
>
> "Don Dally" wrote:
>
>> I have two directories that are identical including file timestamps. One
>> directory is on a remote computer and the other directory is on my local
>> pc.
>> When I get the directory listing and use the -Include filter, I get
>> different
>> results:
>>
>> Local machine:
>> ------------------
>> Command: Get-ChildItem c:\mydir\ -Include *.wav
>> Result: No files returned
>>
>> Remote machine:
>> --------------------
>> Command: Get-ChildItem \\remotemachine\mydir -Include *.wav
>> Result: Returns all the files that match the *.wav mask
>>
>> Other than the path to the directory, these commands are identical. What
>> I
>> don't understand is why the behavior is different from the remote machine
>> to
>> the local machine.
>>
>> To make matters more confusing, the following command works as expected
>> on
>> the local machine:
>>
>> Get-ChildItem *.wav
>>
>> What is it that I don't understand about the -Include switch?
>>
>> Thanks,
>>
>> Don
>>

I'm not able to duplicate the remote machine returning information without
the wildcard on the end of the path are you using RTM PowerShell? If I use
filter instead of include it doesn't matter whether the widcard is present or
not
--
Richard Siddaway

Please note that all scripts are supplied "as is" and with no warranty


"Don Dally" wrote:

> Rich,
>
> Thanks. I missed that in the documentation. The addition of the wildcard on
> the parent object gave me the results I expected.
>
> Now the only curiosity I have is why is the behavior inconsistent when
> dealing with a remote directory?
>
> Don
>
>
> "RichS" <RichS@discussions.microsoft.com> wrote in message
> news:36B45FB8-F789-4350-809D-2242FC4CCFA6@microsoft.com...
> > It seems to work with -include on both local and remote machines if the
> > path
> > specification ends mydir\*
> >
> > This is sort of hinted at in the documentation where is says
> >
> > The Include parameter is effective only when the command includes the
> > Recurse parameter or the path leads to the contents of a directory, such
> > as
> > C:\Windows\*, where the wildcard character specifies the contents of the
> > C:\Windows directory.
> >
> >
> > --
> > Richard Siddaway
> >
> > Please note that all scripts are supplied "as is" and with no warranty
> >
> >
> > "Don Dally" wrote:
> >
> >> I have two directories that are identical including file timestamps. One
> >> directory is on a remote computer and the other directory is on my local
> >> pc.
> >> When I get the directory listing and use the -Include filter, I get
> >> different
> >> results:
> >>
> >> Local machine:
> >> ------------------
> >> Command: Get-ChildItem c:\mydir\ -Include *.wav
> >> Result: No files returned
> >>
> >> Remote machine:
> >> --------------------
> >> Command: Get-ChildItem \\remotemachine\mydir -Include *.wav
> >> Result: Returns all the files that match the *.wav mask
> >>
> >> Other than the path to the directory, these commands are identical. What
> >> I
> >> don't understand is why the behavior is different from the remote machine
> >> to
> >> the local machine.
> >>
> >> To make matters more confusing, the following command works as expected
> >> on
> >> the local machine:
> >>
> >> Get-ChildItem *.wav
> >>
> >> What is it that I don't understand about the -Include switch?
> >>
> >> Thanks,
> >>
> >> Don
> >>
>
>
>

I am running the RTM version. Is using filter functionally the same
as -Include? If not, do you know the differences?

"RichS" <RichS@discussions.microsoft.com> wrote in message
news3B7C47C-B0BE-4CFC-B954-855D3BEE4A29@microsoft.com...
> I'm not able to duplicate the remote machine returning information without
> the wildcard on the end of the path are you using RTM PowerShell? If I
> use
> filter instead of include it doesn't matter whether the widcard is present
> or
> not
> --
> Richard Siddaway
>
> Please note that all scripts are supplied "as is" and with no warranty
>
>
> "Don Dally" wrote:
>
>> Rich,
>>
>> Thanks. I missed that in the documentation. The addition of the wildcard
>> on
>> the parent object gave me the results I expected.
>>
>> Now the only curiosity I have is why is the behavior inconsistent when
>> dealing with a remote directory?
>>
>> Don
>>
>>
>> "RichS" <RichS@discussions.microsoft.com> wrote in message
>> news:36B45FB8-F789-4350-809D-2242FC4CCFA6@microsoft.com...
>> > It seems to work with -include on both local and remote machines if
>> > the
>> > path
>> > specification ends mydir\*
>> >
>> > This is sort of hinted at in the documentation where is says
>> >
>> > The Include parameter is effective only when the command includes the
>> > Recurse parameter or the path leads to the contents of a directory,
>> > such
>> > as
>> > C:\Windows\*, where the wildcard character specifies the contents of
>> > the
>> > C:\Windows directory.
>> >
>> >
>> > --
>> > Richard Siddaway
>> >
>> > Please note that all scripts are supplied "as is" and with no warranty
>> >
>> >
>> > "Don Dally" wrote:
>> >
>> >> I have two directories that are identical including file timestamps.
>> >> One
>> >> directory is on a remote computer and the other directory is on my
>> >> local
>> >> pc.
>> >> When I get the directory listing and use the -Include filter, I get
>> >> different
>> >> results:
>> >>
>> >> Local machine:
>> >> ------------------
>> >> Command: Get-ChildItem c:\mydir\ -Include *.wav
>> >> Result: No files returned
>> >>
>> >> Remote machine:
>> >> --------------------
>> >> Command: Get-ChildItem \\remotemachine\mydir -Include *.wav
>> >> Result: Returns all the files that match the *.wav mask
>> >>
>> >> Other than the path to the directory, these commands are identical.
>> >> What
>> >> I
>> >> don't understand is why the behavior is different from the remote
>> >> machine
>> >> to
>> >> the local machine.
>> >>
>> >> To make matters more confusing, the following command works as
>> >> expected
>> >> on
>> >> the local machine:
>> >>
>> >> Get-ChildItem *.wav
>> >>
>> >> What is it that I don't understand about the -Include switch?
>> >>
>> >> Thanks,
>> >>
>> >> Don
>> >>
>>
>>
>>

They are very similar in effect - filter works when retrieving objects rather
than PowerShell applying a filter after retreiveal and before display
--
Richard Siddaway

Please note that all scripts are supplied "as is" and with no warranty


"Don Dally" wrote:

> I am running the RTM version. Is using filter functionally the same
> as -Include? If not, do you know the differences?
>
> "RichS" <RichS@discussions.microsoft.com> wrote in message
> news3B7C47C-B0BE-4CFC-B954-855D3BEE4A29@microsoft.com...
> > I'm not able to duplicate the remote machine returning information without
> > the wildcard on the end of the path are you using RTM PowerShell? If I
> > use
> > filter instead of include it doesn't matter whether the widcard is present
> > or
> > not
> > --
> > Richard Siddaway
> >
> > Please note that all scripts are supplied "as is" and with no warranty
> >
> >
> > "Don Dally" wrote:
> >
> >> Rich,
> >>
> >> Thanks. I missed that in the documentation. The addition of the wildcard
> >> on
> >> the parent object gave me the results I expected.
> >>
> >> Now the only curiosity I have is why is the behavior inconsistent when
> >> dealing with a remote directory?
> >>
> >> Don
> >>
> >>
> >> "RichS" <RichS@discussions.microsoft.com> wrote in message
> >> news:36B45FB8-F789-4350-809D-2242FC4CCFA6@microsoft.com...
> >> > It seems to work with -include on both local and remote machines if
> >> > the
> >> > path
> >> > specification ends mydir\*
> >> >
> >> > This is sort of hinted at in the documentation where is says
> >> >
> >> > The Include parameter is effective only when the command includes the
> >> > Recurse parameter or the path leads to the contents of a directory,
> >> > such
> >> > as
> >> > C:\Windows\*, where the wildcard character specifies the contents of
> >> > the
> >> > C:\Windows directory.
> >> >
> >> >
> >> > --
> >> > Richard Siddaway
> >> >
> >> > Please note that all scripts are supplied "as is" and with no warranty
> >> >
> >> >
> >> > "Don Dally" wrote:
> >> >
> >> >> I have two directories that are identical including file timestamps.
> >> >> One
> >> >> directory is on a remote computer and the other directory is on my
> >> >> local
> >> >> pc.
> >> >> When I get the directory listing and use the -Include filter, I get
> >> >> different
> >> >> results:
> >> >>
> >> >> Local machine:
> >> >> ------------------
> >> >> Command: Get-ChildItem c:\mydir\ -Include *.wav
> >> >> Result: No files returned
> >> >>
> >> >> Remote machine:
> >> >> --------------------
> >> >> Command: Get-ChildItem \\remotemachine\mydir -Include *.wav
> >> >> Result: Returns all the files that match the *.wav mask
> >> >>
> >> >> Other than the path to the directory, these commands are identical.
> >> >> What
> >> >> I
> >> >> don't understand is why the behavior is different from the remote
> >> >> machine
> >> >> to
> >> >> the local machine.
> >> >>
> >> >> To make matters more confusing, the following command works as
> >> >> expected
> >> >> on
> >> >> the local machine:
> >> >>
> >> >> Get-ChildItem *.wav
> >> >>
> >> >> What is it that I don't understand about the -Include switch?
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Don
> >> >>
> >>
> >>
> >>
>
>
>