Vista - Retrieving file count from a list of child folders

All,

I am fighting some other fires this morning, and hoping for a quick assist.

I need to do file counts on all the subfolders in a target folder.

For a single forlder, this works
(Get-ChildItem C:\Scripts).Count

but when I add recurse, it simply returns a single filecount for all child
folders combined.
(Get-ChildItem C:\Scripts -recurse).Count


How would I modify this to return file counts for individual child folders?


Regards,

Pete Zerger, MCSE(Messaging) | MCTS(SQL 2005) | MCTS(Opsmgr) | MVP - Opsmgr
URL:http://www.systemcenterforum.org
User Group: http://www.systemcenterusergroup.com
MP Catalog: http://www.systemcenterforum.org/mps
Tools: http://www.systemcenterforum.org/tools/

(Get-ChildItem C:\Scripts).Count - returns file and folder count.

try this:
dir | ?{$_.psiscontainer} | %{@{$_.name=(dir $_ | ?{$_.psiscontainer -eq
$false}).count}}

enjoy!
--
WBR, Vadims Podans
PowerShell blog - www.sysadmins.lv

"Pete Zerger (MVP)" <pete.zerger@xxxxxx> rakstīja ziņojum�
"news:265ff311130be8cb558f6a83feaa@xxxxxx"...

You could also try this

$fso = New-Object -com "Scripting.FileSystemObject"
$f = $fso.GetFolder("C:\scripts")
foreach ($folder in $f.subfolders){Write-Host $folder.Path $((get-childitem
$folder.path).count)}

--
Richard Siddaway
All scripts are supplied "as is" and with no warranty
PowerShell MVP
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Vadims Podans" wrote:

Another way, just for the fun of it.

Get-ChildItem -recurse | Where {!$_.PSIsContainer} | Group Directory |
Format-Table Name, Count -autosize

"Pete Zerger (MVP)" wrote:

Hello Pete,

Three great answers to only one question. My expectations are exceeded on
every visit to this newsgroup. Keep up the great work!

Regards,

Pete Zerger, MCSE(Messaging) | MCTS(SQL 2005) | MCTS(Opsmgr) | MVP - Opsmgr
URL:http://www.systemcenterforum.org
User Group: http://www.systemcenterusergroup.com
MP Catalog: http://www.systemcenterforum.org/mps
Tools: http://www.systemcenterforum.org/tools/

Hello Pete,
I hate to ask, but are you talking to yourself, or are you just schizophrenic?

PaulChavez <PaulChavez@xxxxxx> wrote:
When trying the solutions proposed above, I invoked the following
script and got some mysterious shell error when I swapped the code of
solution 2 with solution 1. Both solutions work well for themself.
Could anybody explain the error message to me? Powershell says
something that format-table caused a problem with the standard
formatting.

---------- cut here ------------

# this script works as expected when solution 2 is called before
solution 1
# but there exists some shell error when solution 1 is called before
solution 2. Why?

cls
$mypath="C:\tmp"

#solution 2
Get-ChildItem -recurse $mypath | Where {!$_.PSIsContainer} |
Group-Object Directory |Format-Table Name, Count -autosize

#solution 1
Get-ChildItem -recurse $mypath | Where {$_.psiscontainer} |Foreach {
@{ $_.Name = (dir $_.FullName | Where { $_.psiscontainer -eq $false}
).count}}

---------- cut here ------------


Thanks for any explanation.

Thorsten

What's happening is that the output of both commands are being combined (they're executed within a script) and neither, the outputter nor the formatter, don't know how to handle the second stream, because it's expecting a specific set of format elements but the second stream emits different ones that are incompatible with the first set. Usually, PowerShell handles this by delivering the output as a List, but not when the initial stream is emitted as a Table.
As you already discover swapping the order of the commands can resolve the problem, but it's easier to separate the streams.
To separate the streams you can _pipe_ the first one to a) Out-Default if you want to write/capture it, or b) Write-Host if you just want it displayed.

# reproduce the behavior in the console by executing both commands
# in one line at a time
# PS outputs the 2nd stream as a List
@{key = 'val1'}; get-process

# 1st stream as a HashTable, 2nd as a Table ...PS chokes
@{key = 'val1'}; get-process | ft

# 1st stream as a HashTable, 2nd as a List ...PS chokes
@{key = 'val1'}; get-process | fl

# separate the streams with Out-Default
# PS outputs both streams fine
@{key = 'val1'} | out-default; get-process
@{key = 'val1'} | out-default; get-process | ft

# 1st stream as a Table to Out-Default,
# 2nd as a List ...no problem
@{key = 'val1'} | out-default; get-process | fl

--
Kiron

"Kiron" <Kiron@xxxxxx> wrote:
Ok, thank you for your explanation.

Thorsten