Difference in handling Get-ChildItem between PowerShell and PowerShell ISE?

Asked Sep 21 '16 at 16:19

Active Sep 21 '16 at 17:38

Viewed 71 times

I'm getting a difference in the handling of Get-ChildItem between running it in a PowerShell window and in the PowerShell ISE

Test directory with 5 fives, test01.txt though test05.txt

$orbdata = 'C:\spool\RBDEV\data'
$srcfiles = @(Get-ChildItem -Path $orbdata -Filter *.txt)
$srcfiles.Length

In PowerShell window, I get the result I expected, i.e. 5

But in the ISE, same script gives result 54, i.e. the length of the string ...

test01.txt test02.txt test03.txt test04.txt test05.txt

Any suggestion as to why? ... and even better, how to fix it!

edited Sep 21 '16 at 17:38

Matt

asked Sep 21 '16 at 16:19

SteveC

1

Something is missing here. If nothing else this script is incomplete since we don't see `$orbdata`. No, it should not matter but what you describe should not happen. What PowerShell version are you using. – Matt Sep 21 '16 at 16:28
1

@Matt if `$orbdata = '.'`, it could happen :) – Mathias R. Jessen Sep 21 '16 at 16:31
@matt got v5 installed – SteveC Sep 21 '16 at 16:33
ISE starts in a different directory, apparently. – wOxxOm Sep 21 '16 at 16:40
@SteveC We still don't know what `$orbdata` is – Mathias R. Jessen Sep 21 '16 at 16:41
if path is the same then the only difference has to be permissions related – Jimbo Sep 21 '16 at 17:05
I think it should be ... $orbdata = 'C:\spool\RBDEV\data' – SteveC Sep 21 '16 at 17:17
@MathiasR.Jessen You can reproduce this? – Matt Sep 21 '16 at 17:38
Exactly the same script? That would happen if you did `"$srcfiles".Length`, or something else similar to force the array into a string. – TessellatingHeckler Sep 21 '16 at 18:57
1

I can't reproduce it. – Bill_Stewart Sep 21 '16 at 19:22

0 Answers0