The function defaults to the local path and gets a collection of all of the top level folders, that is, those found directly in the root. The function then takes the collection of folders and pipes them to ForEach-Object. Most of the time we only use the Process scriptblock with ForEach-Object, but I want to take advantage of the Begin and End blocks as well. In the Begin scriptblock I measure all of the files in the root of the parent path and create a custom object that shows the number of files and total size in bytes. I'm going to get this same information for each child folder as well.<\/p>\n
The process scriptblock does just that for each top level folder. This version of my function uses Write-Progress to display progress and in the End script block I have code to complete the progress bar, although It works just fine without it.<\/p>\n
Other techniques I'd like to point out are the use of splatting and error handling. You'll notice that I'm using the common -ErrorVariable parameter. After exploring the different types of exceptions I decided I could easily display any errors and the paths In the Catch block. I'm using Write-Warning, but this could just as easily be written to a text file.<\/p>\n
The function writes an object like this for every folder.<\/p>\n
Path : C:\\windows\\Inf\r\nName : Inf\r\nSize : 81926300\r\nCount : 1265\r\nAttributes : Directory<\/pre>\nHere's an example of complete output:<\/p>\n
![\"foldersize\"](\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2013\/05\/foldersize.png\")
<\/a>Because I've written objects to the pipeline, I could pipe this to Out-Gridview, export to a CSV file or create an HTML report.<\/p>\n