Duplicating Directory Trees

Just updated the "Chronicles of a Script" post
Anyway, you can duplicate an exisiting directory tree (folders only)
to another location with this command

Copy-Item $env:windir -filter {$_.PSIsContainer}
d:\testingpath -recurse -force

$hay
http://scriptolog.blogspot.com

"$hay" <no@addre.ss> wrote in message
news:OoAOyFbNHHA.4992@TK2MSFTNGP04.phx.gbl...
> Just updated the "Chronicles of a Script" post
> Anyway, you can duplicate an exisiting directory tree (folders only)
> to another location with this command
>
> Copy-Item $env:windir -filter {$_.PSIsContainer}
> d:\testingpath -recurse -force

This command does the same thing:

Copy-Item $env:windir -filter {$null} d:\testingpath -recurse -force

I don't think the scriptblock you are specifying for -filter is behaving
like you think it is.

--
Keith

"Keith Hill [MVP]" <r_keith_hill@no.spam.thank.u.hotmail.com> wrote in
message news:OWcFOTbNHHA.1240@TK2MSFTNGP03.phx.gbl...
> "$hay" <no@addre.ss> wrote in message
> news:OoAOyFbNHHA.4992@TK2MSFTNGP04.phx.gbl...
>> Just updated the "Chronicles of a Script" post
>> Anyway, you can duplicate an exisiting directory tree (folders only)
>> to another location with this command
>>
>> Copy-Item $env:windir -filter {$_.PSIsContainer}
>> d:\testingpath -recurse -force
>
> This command does the same thing:
>
> Copy-Item $env:windir -filter {$null} d:\testingpath -recurse -force

And so does this:

Copy-Item $env:windir -filter '$null' d:\testingpath -recurse -force

The parameter type of -filter is string, so when you specify a scriptblock I
think you are getting just the "ToString()" representation of the
scriptblock e.g.:

344> {$_.PSIsContainer}.ToString()
$_.PSIsContainer

What made me wonder on this is that you were using $_ which in the context
of your command wouldn't represent a valid value i.e. the command starts the
pipeline and doesn't receive pipeline objects.

--
Keith

OK, Keith, I'll bite.

copy-item $env:windir -filter "anything" -destination C:\TestingPath6
-force -recurse

also copies directories only.

Yet if you omit the filter parameter files are copied too.

Do you understand why? At the moment I can't figure it out.

Andrew Watt MVP

On Thu, 11 Jan 2007 12:20:52 -0700, "Keith Hill [MVP]"
<r_keith_hill@no.spam.thank.u.hotmail.com> wrote:

>"Keith Hill [MVP]" <r_keith_hill@no.spam.thank.u.hotmail.com> wrote in
>message news:OWcFOTbNHHA.1240@TK2MSFTNGP03.phx.gbl...
>> "$hay" <no@addre.ss> wrote in message
>> news:OoAOyFbNHHA.4992@TK2MSFTNGP04.phx.gbl...
>>> Just updated the "Chronicles of a Script" post
>>> Anyway, you can duplicate an exisiting directory tree (folders only)
>>> to another location with this command
>>>
>>> Copy-Item $env:windir -filter {$_.PSIsContainer}
>>> d:\testingpath -recurse -force
>>
>> This command does the same thing:
>>
>> Copy-Item $env:windir -filter {$null} d:\testingpath -recurse -force
>
>And so does this:
>
>Copy-Item $env:windir -filter '$null' d:\testingpath -recurse -force
>
>The parameter type of -filter is string, so when you specify a scriptblock I
>think you are getting just the "ToString()" representation of the
>scriptblock e.g.:
>
>344> {$_.PSIsContainer}.ToString()
>$_.PSIsContainer
>
>What made me wonder on this is that you were using $_ which in the context
>of your command wouldn't represent a valid value i.e. the command starts the
>pipeline and doesn't receive pipeline objects.

copy-item $env:windir -filter *.* -destination
C:\TestingPath6 -force -recurse

certainly did the job.
I have messed with the -exclude parameter instead, using various options and
it didn't worked.
guess i walked the wrong path

Cheers

$hay


"Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
news:6d7dq2ltm5sceo2rm93trd9mv49p2h0ujf@4ax.com...
> OK, Keith, I'll bite.
>
> copy-item $env:windir -filter "anything" -destination C:\TestingPath6
> -force -recurse
>
> also copies directories only.
>
> Yet if you omit the filter parameter files are copied too.
>
> Do you understand why? At the moment I can't figure it out.
>
> Andrew Watt MVP
>
> On Thu, 11 Jan 2007 12:20:52 -0700, "Keith Hill [MVP]"
> <r_keith_hill@no.spam.thank.u.hotmail.com> wrote:
>
>>"Keith Hill [MVP]" <r_keith_hill@no.spam.thank.u.hotmail.com> wrote in
>>message news:OWcFOTbNHHA.1240@TK2MSFTNGP03.phx.gbl...
>>> "$hay" <no@addre.ss> wrote in message
>>> news:OoAOyFbNHHA.4992@TK2MSFTNGP04.phx.gbl...
>>>> Just updated the "Chronicles of a Script" post
>>>> Anyway, you can duplicate an exisiting directory tree (folders only)
>>>> to another location with this command
>>>>
>>>> Copy-Item $env:windir -filter {$_.PSIsContainer}
>>>> d:\testingpath -recurse -force
>>>
>>> This command does the same thing:
>>>
>>> Copy-Item $env:windir -filter {$null} d:\testingpath -recurse -force
>>
>>And so does this:
>>
>>Copy-Item $env:windir -filter '$null' d:\testingpath -recurse -force
>>
>>The parameter type of -filter is string, so when you specify a scriptblock
>>I
>>think you are getting just the "ToString()" representation of the
>>scriptblock e.g.:
>>
>>344> {$_.PSIsContainer}.ToString()
>>$_.PSIsContainer
>>
>>What made me wonder on this is that you were using $_ which in the context
>>of your command wouldn't represent a valid value i.e. the command starts
>>the
>>pipeline and doesn't receive pipeline objects.

"Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
news:6d7dq2ltm5sceo2rm93trd9mv49p2h0ujf@4ax.com...
> OK, Keith, I'll bite.
>
> copy-item $env:windir -filter "anything" -destination C:\TestingPath6
> -force -recurse
>
> also copies directories only.
>
> Yet if you omit the filter parameter files are copied too.
>
> Do you understand why? At the moment I can't figure it out.

Neither can I. :-(

--
Keith