Here it is:
$files = Get-ChildItem . -Recurse | `
where-Object {$_.Name -match "^.+\.cs$"}
$processedfiles = @();
$totalLines = 0;
foreach ($x in $files)
{
$name= $x.Name;
$lines= (Get-Content ($x.Fullname) | `
Measure-Object –Line ).Lines;
$object = New-Object Object;
$object | Add-Member -MemberType noteproperty `
-name Name -value $name;
$object | Add-Member -MemberType noteproperty `
-name Lines -value $lines;
$processedfiles += $object;
$totalLines += $lines;
}
$processedfiles | Where-Object {$_.Lines -gt 100} | `
sort-object -property Lines -Descending
Write-Host ... ... ... ... ...
Write-Host Total Lines $totalLines In Files $processedfiles.count
Line 00: Will get all the .cs files from the current working folder and below.
Line 07: Uses the measure-object cmdlet to get the number of lines in the current file being processed.
Line 09: Creates an object, lines 10 and 12 dynamically adds properties to that object for the file name and the line count.
Line 11: Adds the new object to the end of the array of processed files.
Line 17: Selects all the files from the array where the line count is greater than 100 (an arbitary amount, i only care about files longer than roughly 2 screens worth of text), Then print them out in descending order of line count.
My results:
our current project has a total of 154068 lines of code in .cs files.
2559 .cs files of which 312 files have a line count greater than 100 lines.
16 files are over 400 lines in length, but none of those were in the main product (All the worst classes are test classes and helpers which are not production code).
I also wondered about the state of my views:
320 .cshtml files a total of 10958 lines, the vast majority are less than 100 and only 6 over 150.