{"id":510,"date":"2009-11-16T11:30:24","date_gmt":"2009-11-16T16:30:24","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/?p=510"},"modified":"2009-11-16T11:39:24","modified_gmt":"2009-11-16T16:39:24","slug":"all-hail-dir-usealot","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/","title":{"rendered":"All Hail Dir UseALot!"},"content":{"rendered":"

Some of you know my relationship with the a command prompt goes back a long, long way. Naturally I became very adept at using the DIR command, fully taking advantage of its switches to tease out hidden information or to quickly get just the information I wanted. When PowerShell first came out, I made the transition to the DIR alias without too much difficulty. Although I still found myself wanting to run a command like DIR \/ad\u00a0 (ie list only directories). Yes, you can achieve the same results with the PowerShell cmdlets, but that takes too much typing, especially for something I might want to use on a regular basis. I finally got around to writing a DIR function for PowerShell that better emulates my beloved DIR command from the CMD shell.<\/p>\n

The function is called Get-FolderItem, although when I load the function I also create aliases pdir and gfi. This is a PowerShell v2 function complete with help and examples.<\/p>\n

\"captured_Image.png\"<\/a><\/p>\n

Here\u2019s the code listing then I\u2019ll explain a few highlights.<\/p>\n

\n
\n
Function Get-FolderItem {<\/pre>\n
<\/p>\n
#requires -version 2.0<\/span><\/pre>\n
<\/p>\n
<\/p>\n
<#<\/span><\/pre>\n
<\/p>\n
.Synopsis<\/pre>\n
<\/p>\n
    A PowerShell version of the DIR command from the CMD shell that supports sorting and filtering.<\/pre>\n
<\/p>\n
.Description<\/pre>\n
<\/p>\n
    The DIR command from the CMD shell has useful parameters to sort output by date, \/od, by size \/os and by<\/pre>\n
<\/p>\n
    name \/on. PowerShell's Get-ChildItem needs to pipe output to other cmdlets to achieve the same results. <\/span><\/pre>\n
<\/p>\n
    This function offers a shortcut. This function also supports the equivalent of \/b, \/a, and \/q. You may<\/pre>\n
<\/p>\n
    need to pipe the function to other cmdlets like Format-Table or Select-Object to achieve the exact results<\/pre>\n
<\/p>\n
    you want.<\/pre>\n
<\/p>\n
<\/p>\n
    This function includes a custom format PS1XML file, psdir.FileSystem.Format.ps1xml, that should be stored<\/pre>\n
<\/p>\n
    in your profile folder. When you use the -owner parameter, the custom format file is loaded so that<\/pre>\n
<\/p>\n
    owner information is displayed by default. You can also pipe output to Format-Table or Format-List and<\/pre>\n
<\/p>\n
    get Owner information. The original formatting file is reloaded before the function ends.<\/pre>\n
<\/p>\n
<\/p>\n
    This function supports -Verbose. Use it to troubleshoot or debug the function.<\/pre>\n
<\/p>\n
.Parameter Path<\/pre>\n
<\/p>\n
    Enter a folder path. The default is the current directory.<\/pre>\n
<\/p>\n
.Parameter Filter<\/pre>\n
<\/p>\n
    A file filter like *.txt.  The default *.*<\/pre>\n
<\/p>\n
.Parameter Order<\/pre>\n
<\/p>\n
    The attribute to sort on. Possible values are d[ate],s[ize],e[xtension] and n[ame], which is the default.<\/pre>\n
<\/p>\n
    Prepend -- before the value, ie --date to sort in reverse order. This parameter has an alias of 'o'<\/span><\/pre>\n
<\/p>\n
.Parameter Attribute<\/pre>\n
<\/p>\n
    Get a directory listing based on an attribute such as a[rchive], d[irectory], h[idden], s[system] and<\/pre>\n
<\/p>\n
    r[ead]. Equivalent to \/A. Use -- before a value to return results NOT matching. For example, to find<\/pre>\n
<\/p>\n
    all files without the archive attribute set use -attribute --a. You can also combine attributes, for<\/pre>\n
<\/p>\n
    example -attribute dhr to return only read-only and hidden directories. Using this parameter may still<\/pre>\n
<\/p>\n
    display hidden and system files. For example, if you search for attribute 'a', any hidden or system<\/span><\/pre>\n
<\/p>\n
    files with this attribute will also be displayed.<\/pre>\n
<\/p>\n
.Parameter Bare<\/pre>\n
<\/p>\n
    Display full path only. Equivalent to \/B. This parameter cannot be used with any other parameters.<\/pre>\n
<\/p>\n
.Parameter Owner<\/pre>\n
<\/p>\n
    Adds the owner of each file or folder.<\/pre>\n
<\/p>\n
<\/p>\n
    This function includes a custom format PS1XML file, psdir.FileSystem.Format.ps1xml, that should be stored<\/pre>\n
<\/p>\n
    in your $profile folder. When you use the -owner parameter, the custom format file is loaded so that<\/pre>\n
<\/p>\n
    owner information is displayed by default. You can also pipe output to Format-Table or Format-List and<\/pre>\n
<\/p>\n
    get Owner information. The original formatting file is reloaded before the function ends.<\/pre>\n
<\/p>\n
.Parameter Recurse<\/pre>\n
<\/p>\n
    Recursively search the path.<\/pre>\n
<\/p>\n
<\/p>\n
.Example<\/pre>\n
<\/p>\n
PS C:\\> get-folderitem -order date<\/pre>\n
<\/p>\n
<\/p>\n
Display files in the current directory sorted by date.<\/pre>\n
<\/p>\n
<\/p>\n
.Example<\/pre>\n
<\/p>\n
PS C:\\> get-folderitem c:\\scripts *.ps1 -order --size -recurse<\/pre>\n
<\/p>\n
<\/p>\n
Recursively search the scripts the directory for all PowerShell files and display output sorted by size in descending order.<\/pre>\n
<\/p>\n
<\/p>\n
.Example<\/pre>\n
<\/p>\n
PS C:\\> gfi f:\\files -owner -recurse | Sort Owner | Select Owner,FullName,Length,CreationTime,LastWriteTime<\/pre>\n
<\/p>\n
<\/p>\n
Search files under F:\\Files and display the full filename, the owner, the file size, when it was created and when<\/pre>\n
<\/p>\n
it was last modified. The results are sorted by owner.<\/pre>\n
<\/p>\n
<\/p>\n
.Example<\/pre>\n
<\/p>\n
PS C:\\> get-folderitem f:\\files -recurse -attribute a -bare<\/pre>\n
<\/p>\n
<\/p>\n
Search F:\\files for all files with an attribute of A and use a bare file listing.<\/pre>\n
<\/p>\n
<\/p>\n
.Inputs<\/pre>\n
<\/p>\n
Accepts strings of folder names<\/pre>\n
<\/p>\n
.Outputs<\/pre>\n
<\/p>\n
File and Folder objects<\/pre>\n
<\/p>\n
<\/p>\n
.Link<\/pre>\n
<\/p>\n
http:\/\/jdhitsolutions.com\/blog\/<\/pre>\n
<\/p>\n
<\/p>\n
.Link<\/pre>\n
<\/p>\n
Get-ChildItem<\/pre>\n
<\/p>\n
<\/p>\n
.Notes<\/pre>\n
<\/p>\n
NAME:      Get-FolderItem<\/pre>\n
<\/p>\n
VERSION:   1.0<\/pre>\n
<\/p>\n
AUTHOR:    Jeffery Hicks  http:\/\/jdhitsolutions.com\/blog<\/pre>\n
<\/p>\n
LASTEDIT:  11\/16\/2009<\/pre>\n
<\/p>\n
<\/p>\n
<\/p>\n
#><\/pre>\n
<\/p>\n
<\/p>\n
[CmdletBinding(DefaultParameterSetName=\"Set1\")]<\/pre>\n
<\/p>\n
<\/p>\n
#define the parameters<\/pre>\n
<\/p>\n
Param (<\/pre>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$True, ValueFromPipelineByPropertyName=$True,<\/pre>\n
<\/p>\n
  Position=0,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\",<\/pre>\n
<\/p>\n
  HelpMessage=\"Enter a folder path\")]<\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\",Position=0)]<\/pre>\n
<\/p>\n
  [ValidateScript({<\/pre>\n
<\/p>\n
    if ( (Test-Path $_) -AND ((Get-Item $_).PSProvider.Name -eq \"FileSystem\")) {<\/pre>\n
<\/p>\n
       $True<\/pre>\n
<\/p>\n
   } else {<\/pre>\n
<\/p>\n
      Write-Warning \"Can't find $_ or verify that it is a FileSystem PSDrive.\"<\/span><\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
   } )]<\/pre>\n
<\/p>\n
  [String[]]$Path=\".\",<\/span><\/pre>\n
<\/p>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Position=1,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\",<\/span><\/pre>\n
<\/p>\n
  HelpMessage=\"A file filter<\/span> like *.txt\")] <\/span><\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\", Position=1)] <\/span><\/pre>\n
<\/p>\n
  [String]$Filter=\"*.*\",<\/span><\/pre>\n
<\/p>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\",<\/span><\/pre>\n
<\/p>\n
  HelpMessage=\"Sort order. Possible values are date,size,extension and name, which is the default<\/span>.<\/pre>\n
<\/p>\n
  Prepend a -- sign before the value, ie --date to sort in<\/span> reverse order.\")]<\/span><\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\")] <\/span><\/pre>\n
<\/p>\n
  [Alias(\"o\")] <\/span><\/pre>\n
<\/p>\n
  [ValidateSet(\"date\",\"<\/span>size\",\"<\/span>extension\",\"<\/span>name\",\"<\/span>--date\",\"<\/span>--size\",\"<\/span>--extension\",\"<\/span>--name\")]<\/span><\/pre>\n
<\/p>\n
  [string]$Order=\"name\",<\/span><\/pre>\n
<\/p>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\",<\/span><\/pre>\n
<\/p>\n
  HelpMessage=\"Select a file or folder attribute.\")] <\/span><\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\")] <\/span><\/pre>\n
<\/p>\n
  [ValidateScript( { foreach ($a in ($_.ToCharArray())) {<\/pre>\n
<\/p>\n
     If (! (\"-darhs\").contains($a)) {<\/span><\/pre>\n
<\/p>\n
       Write-Warning \"Valid attributes are d,a,r,h and s.\"<\/span><\/pre>\n
<\/p>\n
     }<\/pre>\n
<\/p>\n
     else {$True}<\/pre>\n
<\/p>\n
     }<\/pre>\n
<\/p>\n
   })]<\/pre>\n
<\/p>\n
  [String]$Attribute,<\/pre>\n
<\/p>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\",<\/span><\/pre>\n
<\/p>\n
  HelpMessage=\"Recursively search the path.\")] <\/span><\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\")] <\/span><\/pre>\n
<\/p>\n
  [Switch]$Recurse,<\/pre>\n
<\/p>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set2\",<\/span><\/pre>\n
<\/p>\n
  HelpMessage=\"Select a file or folder attribute.\")] <\/span><\/pre>\n
<\/p>\n
  [Switch]$Bare,<\/pre>\n
<\/p>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\",<\/span><\/pre>\n
<\/p>\n
  HelpMessage=\"Add the file owner as a new property.\")] <\/span><\/pre>\n
<\/p>\n
  [Switch]$Owner<\/pre>\n
<\/p>\n
<\/p>\n
 )<\/pre>\n
<\/p>\n
<\/p>\n
 #Start Main Function Body<\/pre>\n
<\/p>\n
 Begin {<\/pre>\n
<\/p>\n
<\/p>\n
        Write-Verbose \"Processing BEGIN Script Block\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        #define the path to the custom format file<\/pre>\n
<\/p>\n
        $profileDir=Split-Path $profile<\/pre>\n
<\/p>\n
        $formatfile=\"$profiledir\\pdir.FileSystem.format.ps1xml\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        #check for -- at the beginning of the $order parameter<\/pre>\n
<\/p>\n
        if ($order.substring(0,2) -match \"--\" ) {<\/span><\/pre>\n
<\/p>\n
            Write-Verbose \"descending is True\"<\/span><\/pre>\n
<\/p>\n
            $descending=$True<\/pre>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
<\/p>\n
        Write-Verbose \"Evaluating $order\"       <\/span><\/pre>\n
<\/p>\n
        #evaluate parameters<\/pre>\n
<\/p>\n
        switch -regex ($Order) {<\/pre>\n
<\/p>\n
        \"name$\" {$sort=\"<\/span>name\";break}<\/span><\/pre>\n
<\/p>\n
        \"date$\" {$sort=\"<\/span>LastWriteTime\";break}<\/span><\/pre>\n
<\/p>\n
        \"size$\" {$sort=\"<\/span>Length\";break}<\/span><\/pre>\n
<\/p>\n
        \"extension$\" {$sort=\"<\/span>extension\";break}<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        default {<\/pre>\n
<\/p>\n
            #this warning should never be reached but just in case...<\/pre>\n
<\/p>\n
            Write-Warning \"Invalid value $order for<\/span> Order parameter. Valid choices are date,name,size and extension. Use --value to sort in<\/span> reverse order.\"<\/span><\/pre>\n
<\/p>\n
            $fail=$True<\/pre>\n
<\/p>\n
            return<\/pre>\n
<\/p>\n
            }<\/pre>\n
<\/p>\n
        } #end switch<\/pre>\n
<\/p>\n
<\/p>\n
        Write-Verbose \"Sorting on $sort\"<\/span><\/pre>\n
<\/p>\n
        Write-Verbose \"Initializing `$data\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        #initialize results variable<\/pre>\n
<\/p>\n
        $data=@()<\/pre>\n
<\/p>\n
<\/p>\n
       Write-Verbose \"Exiting BEGIN script<\/span> block\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
} #end Begin<\/pre>\n
<\/p>\n
<\/p>\n
Process {<\/pre>\n
<\/p>\n
<\/p>\n
    #bail if $fail was found, but this should never happen<\/pre>\n
<\/p>\n
    if ($fail) {return}<\/pre>\n
<\/p>\n
<\/p>\n
        If ($_) {<\/pre>\n
<\/p>\n
            Write-Verbose \"Assigning pipelined input to `$Path\"<\/span><\/pre>\n
<\/p>\n
            $Path=$_<\/pre>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
<\/p>\n
      Write-Verbose \"Getting files $filter<\/span> from root of $path\"<\/span><\/pre>\n
<\/p>\n
      #get files from root directory of $path<\/pre>\n
<\/p>\n
      $data+=Get-ChildItem -Path $path -Filter $Filter -force<\/pre>\n
<\/p>\n
<\/p>\n
      if ($Recurse) {<\/pre>\n
<\/p>\n
         Write-Verbose \"Getting files recursively\"<\/span><\/pre>\n
<\/p>\n
         $data+= Get-ChildItem $Path -Recurse -Force | where {$_.PSIsContainer} | foreach {<\/pre>\n
<\/p>\n
          Write-Verbose \"Processing $($_.fullname)\"<\/span><\/pre>\n
<\/p>\n
          Get-ChildItem $_.FullName -filter $Filter -force<\/pre>\n
<\/p>\n
        } #end ForEach<\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
    Write-Verbose \"Finished gathering files\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
} #end Process<\/pre>\n
<\/p>\n
<\/p>\n
End {<\/pre>\n
<\/p>\n
    Write-Verbose \"Processing END script<\/span> block\"<\/span><\/pre>\n
<\/p>\n
    #filter and sort as necessary and write final objects to the pipeline<\/pre>\n
<\/p>\n
<\/p>\n
    #filter by attributes and turn attribute values into a character array<\/pre>\n
<\/p>\n
    if ($Attribute -AND $attribute.StartsWith(\"--\")) {<\/span><\/pre>\n
<\/p>\n
        Write-Verbose \"Getting files that match $attribute\"<\/span><\/pre>\n
<\/p>\n
        $modes=$Attribute.Substring(2).ToCharArray()<\/pre>\n
<\/p>\n
<\/p>\n
        #get the first attribute and filter<\/pre>\n
<\/p>\n
        Write-Verbose \"Filtering for<\/span> $($modes[0])\"<\/span><\/pre>\n
<\/p>\n
        $data=$data | where {$_.mode -notmatch $modes[0]}<\/pre>\n
<\/p>\n
<\/p>\n
<\/p>\n
        #filter for each additional mode<\/pre>\n
<\/p>\n
        for ($i=1;$i -lt $modes.count;$i++) {<\/pre>\n
<\/p>\n
            Write-Verbose \"Filtering for<\/span> $($modes[$i])\"<\/span><\/pre>\n
<\/p>\n
            $data=$data | where {$_.mode -notmatch $modes[$i]}<\/pre>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    elseif ($Attribute) {<\/pre>\n
<\/p>\n
       Write-Verbose \"Getting files that match $attribute\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
       $modes=$Attribute.ToCharArray()<\/pre>\n
<\/p>\n
<\/p>\n
       #get the first attribute and filter<\/pre>\n
<\/p>\n
       Write-Verbose \"Filtering for<\/span> $($modes[0])\"<\/span><\/pre>\n
<\/p>\n
       $data=$data | where {$_.mode -match $modes[0]}<\/pre>\n
<\/p>\n
<\/p>\n
<\/p>\n
        #filter for each additional mode<\/pre>\n
<\/p>\n
        for ($i=1;$i -lt $modes.count;$i++) {<\/pre>\n
<\/p>\n
            Write-Verbose \"Filtering for<\/span> $($modes[$i])\"<\/span><\/pre>\n
<\/p>\n
            $data=$data | where {$_.mode -match $modes[$i]}<\/pre>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
        else {<\/pre>\n
<\/p>\n
          Write-Verbose \"Removing system and hidden files since no special attributes were passed.\"<\/span><\/pre>\n
<\/p>\n
          $data=$data | where {$_.Mode -notmatch \"s\" -AND $_.mode -notMatch \"<\/span>h\"}<\/span><\/pre>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
<\/p>\n
<\/p>\n
       #sort all results PSParentPath to keep everything grouped by folder<\/pre>\n
<\/p>\n
<\/p>\n
      If ($descending) {<\/pre>\n
<\/p>\n
          Write-Verbose \"Sorting data by $sort in<\/span> descending order\"<\/span><\/pre>\n
<\/p>\n
          $data = $data | sort -property PSParentPath | sort -property $sort -descending<\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
      Else {<\/pre>\n
<\/p>\n
          Write-Verbose \"Sorting data by $sort\"<\/span><\/pre>\n
<\/p>\n
          $data= $data  | sort -property PSParentPath,$sort<\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
<\/p>\n
       #if $bare write out only the full filename<\/pre>\n
<\/p>\n
       if ($Bare) {<\/pre>\n
<\/p>\n
         Write-Verbose \"Writing data in<\/span> bare mode\"<\/span><\/pre>\n
<\/p>\n
         $data | select FullName<\/pre>\n
<\/p>\n
       }<\/pre>\n
<\/p>\n
      elseif ($owner) {<\/pre>\n
<\/p>\n
        Write-Verbose \"Writing data with owner information\"<\/span><\/pre>\n
<\/p>\n
        Write-Verbose \"Loading custom format File $formatfile\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        Update-FormatData -prepend $formatfile -ea \"SilentlyContinue\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        #add owner information<\/pre>\n
<\/p>\n
         $data | foreach {<\/pre>\n
<\/p>\n
           $_ | Add-Member -MemberType NoteProperty -Name \"Owner\" -value ((Get-ACL $_.fullname).Owner ) -passthru<\/span><\/pre>\n
<\/p>\n
          }<\/pre>\n
<\/p>\n
        #reload original FileSystemFormat<\/pre>\n
<\/p>\n
        Write-Verbose \"Reloading $pshome\\filesystem.format.ps1xml\"<\/span><\/pre>\n
<\/p>\n
        Update-FormatData -prepend $pshome\\filesystem.format.ps1xml -ea \"SilentlyContinue\"<\/span><\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
      else {<\/pre>\n
<\/p>\n
        #just write the results to the pipeline<\/pre>\n
<\/p>\n
         Write-Verbose \"Write results to the pipeline\"<\/span><\/pre>\n
<\/p>\n
          write $data<\/pre>\n
<\/p>\n
         }<\/pre>\n
<\/p>\n
<\/p>\n
     Write-Verbose \"Finished\"<\/pre>\n
<\/p>\n
 } #end END<\/span><\/pre>\n
<\/p>\n
<\/p>\n
} #end function<\/span><\/pre>\n
<\/p>\n
<\/p>\n
Set-Alias pdir Get-FolderItem<\/pre>\n
<\/p>\n
Set-Alias gfi Get-FolderItem<\/pre>\n
<\/div>\n<\/div>\n
The function is really a wrapper for Get-ChildItem<\/a> occasionally combined with Where-Object<\/a>. It takes a file path as the first parameter, defaulting to the current folder if nothing is specified. The parameter includes a validateScript attribute to verify that you are trying to get a directory listing of a FileSystem PSdrive.<\/p>\n
\n
\n
Param (<\/pre>\n
<\/p>\n
  [Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$True, ValueFromPipelineByPropertyName=$True,<\/pre>\n
<\/p>\n
  Position=0,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\"<\/span>,<\/pre>\n
<\/p>\n
  HelpMessage=\"Enter a folder path\"<\/span>)]<\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\"<\/span>,Position=0)]<\/pre>\n
<\/p>\n
  [ValidateScript({<\/pre>\n
<\/p>\n
    if<\/span> ( (Test-Path $_) -AND ((Get-Item $_).PSProvider.Name -eq<\/span> \"FileSystem\"<\/span>)) {<\/pre>\n
<\/p>\n
       $True<\/pre>\n
<\/p>\n
   } else<\/span> {<\/pre>\n
<\/p>\n
      Write-Warning \"Can't find $_ or verify that it is a FileSystem PSDrive.\"<\/span><\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
   } )]<\/pre>\n
<\/p>\n
  [String[]]$Path=\".\"<\/span>,<\/pre>\n
<\/div>\n<\/div>\n
The parameter can also take pipelined input, although I rarely use it that way.<\/p>\n
Unlike the DIR command, I needed to separate out any filtering like *.txt to a separate parameter. It is positional, but only if you specify a path.<\/p>\n
PS C:\\> pdir . *.txt <\/span><\/p>\n
 Directory: C:\\ <\/span><\/p>\n
Mode\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LastWriteTime\u00a0\u00a0\u00a0\u00a0 Length Name<\/span><\/p>\n
----\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -------------\u00a0\u00a0\u00a0\u00a0 ------ ----<\/p>\n
 <\/span><\/p>\n
-a---\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8\/31\/2009\u00a0\u00a0 7:13 AM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 55 computers.txt<\/p>\n
-a---\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 10\/14\/2009\u00a0\u00a0 8:25 AM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 406 FolderACLScan.txt<\/p>\n
-a---\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5\/8\/2009\u00a0\u00a0 8:29 AM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 nvlog.txt<\/span><\/p>\n
You\u2019ll notice the output is what you would expect from Get-ChildItem. The function allows you to sort the output by size, name, date and extension. This is similiar to the \/o parameter from DIR. To sort in reverse order in CMD you would use \/O-d (reverse date order). In my function use \u2013 before the value.<\/p>\n
PS C:\\> pdir \u2013o \u2013date<\/span><\/p>\n
You can use \u2013o by the way because I defined it as an alias.<\/p>\n
\n
\n
[Parameter(<\/pre>\n
<\/p>\n
  ValueFromPipeline=$False,<\/pre>\n
<\/p>\n
  Mandatory=$False,<\/pre>\n
<\/p>\n
  ParameterSetName=\"Set1\"<\/span>,<\/pre>\n
<\/p>\n
  HelpMessage=\"Sort order. Possible values are date,size,extension and name, which is the default. <\/span><\/pre>\n
<\/p>\n
  Prepend a -- sign before the value, ie --date to sort in reverse order.\")]<\/pre>\n
<\/p>\n
  [Parameter(ParameterSetName=\"Set2\"<\/span>)]<\/pre>\n
<\/p>\n
  [Alias(\"o\"<\/span>)]<\/pre>\n
<\/p>\n
  [ValidateSet(\"date\"<\/span>,\"size\"<\/span>,\"extension\"<\/span>,\"name\"<\/span>,\"--date\"<\/span>,\"--size\"<\/span>,\"--extension\"<\/span>,\"--name\"<\/span>)]<\/pre>\n
<\/p>\n
  [string]$Order=\"name\"<\/span>,<\/pre>\n
<\/div>\n<\/div>\n
There is also a ValidateSet attribute to verify the value passed.<\/p>\n
The main part of the function uses Get-ChildItem and saves the results to a variable.<\/p>\n
\n
\n
#get files from root directory of $path<\/span><\/pre>\n
<\/p>\n
    $data+=Get-ChildItem -Path $path -Filter $Filter -force<\/pre>\n
<\/p>\n
<\/p>\n
    if<\/span> ($Recurse) {<\/pre>\n
<\/p>\n
       Write-Verbose \"Getting files recursively\"<\/span><\/pre>\n
<\/p>\n
       $data+= Get-ChildItem $Path -Recurse -Force | where {$_.PSIsContainer} | foreach<\/span> {<\/pre>\n
<\/p>\n
        Write-Verbose \"Processing $($_.fullname)\"<\/span><\/pre>\n
<\/p>\n
        Get-ChildItem $_.FullName -filter<\/span> $Filter -force<\/pre>\n
<\/p>\n
      } #end ForEach<\/span><\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/div>\n<\/div>\n
Once I have the data, then I can apply my filtering and sorting. For example\u00a0 I\u00a0 wanted to be able to filter on file attributes like A, H, or S like the \/A switch in DIR, including the ability to display files that DON\u2019T match and the option to filter on multiple modes like HS. Because I have no way of knowing what combination of modes might be passed or whether I need to find files that don\u2019t match, I split the attribute parameter value into an array and then find files that match (or don\u2019t match) by iterating through the array.<\/p>\n
\n
\n
#filter by attributes and turn attribute values into a character array<\/span><\/pre>\n
<\/p>\n
   if<\/span> ($Attribute -AND $attribute.StartsWith(\"--\"<\/span>)) {<\/pre>\n
<\/p>\n
       Write-Verbose \"Getting files that match $attribute\"<\/span><\/pre>\n
<\/p>\n
       $modes=$Attribute.Substring(2).ToCharArray()<\/pre>\n
<\/p>\n
<\/p>\n
       #get the first attribute and filter<\/span><\/pre>\n
<\/p>\n
       Write-Verbose \"Filtering for $($modes[0])\"<\/span><\/pre>\n
<\/p>\n
       $data=$data | where {$_.mode -notmatch<\/span> $modes[0]}<\/pre>\n
<\/p>\n
<\/p>\n
<\/p>\n
       #filter for each additional mode<\/span><\/pre>\n
<\/p>\n
       for<\/span> ($i=1;$i -lt<\/span> $modes.count;$i++) {<\/pre>\n
<\/p>\n
           Write-Verbose \"Filtering for $($modes[$i])\"<\/span><\/pre>\n
<\/p>\n
           $data=$data | where {$_.mode -notmatch<\/span> $modes[$i]}<\/pre>\n
<\/p>\n
       }<\/pre>\n
<\/p>\n
<\/p>\n
   }<\/pre>\n
<\/p>\n
   elseif<\/span> ($Attribute) {<\/pre>\n
<\/p>\n
      Write-Verbose \"Getting files that match $attribute\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
      $modes=$Attribute.ToCharArray()<\/pre>\n
<\/p>\n
<\/p>\n
      #get the first attribute and filter<\/span><\/pre>\n
<\/p>\n
      Write-Verbose \"Filtering for $($modes[0])\"<\/span><\/pre>\n
<\/p>\n
      $data=$data | where {$_.mode -match<\/span> $modes[0]}<\/pre>\n
<\/p>\n
<\/p>\n
<\/p>\n
       #filter for each additional mode<\/span><\/pre>\n
<\/p>\n
       for<\/span> ($i=1;$i -lt<\/span> $modes.count;$i++) {<\/pre>\n
<\/p>\n
           Write-Verbose \"Filtering for $($modes[$i])\"<\/span><\/pre>\n
<\/p>\n
           $data=$data | where {$_.mode -match<\/span> $modes[$i]}<\/pre>\n
<\/p>\n
       }<\/pre>\n
<\/div>\n<\/div>\n
The data set is revised each time.\u00a0 If no attributes were passed then I clean up the data set to remove hidden and system files. This makes the output more like the regular DIR and Get-Childitem commands.<\/p>\n
\n
\n
else<\/span> {<\/pre>\n
<\/p>\n
         Write-Verbose \"Removing system and hidden files since no special attributes were passed.\"<\/span><\/pre>\n
<\/p>\n
         $data=$data | where {$_.Mode -notmatch<\/span> \"s\"<\/span> -AND $_.mode -notMatch \"h\"<\/span>}<\/pre>\n
<\/p>\n
       }<\/pre>\n
<\/p>\n
<\/div>\n<\/div>\n
All that is really left is to sort the results by the parent folder, again to make the output more like Get-ChildItem. If a sort value was passed, then data is sorted by that value.<\/p>\n
\n
\n
#sort all results PSParentPath to keep everything grouped by folder<\/span><\/pre>\n
<\/p>\n
   If ($descending) {<\/pre>\n
<\/p>\n
       Write-Verbose \"Sorting data by $sort in descending order\"<\/span><\/pre>\n
<\/p>\n
       $data = $data | sort -property PSParentPath | sort -property $sort -descending<\/pre>\n
<\/p>\n
   }<\/pre>\n
<\/p>\n
   Else {<\/pre>\n
<\/p>\n
       Write-Verbose \"Sorting data by $sort\"<\/span><\/pre>\n
<\/p>\n
       $data= $data  | sort -property PSParentPath,$sort<\/pre>\n
<\/p>\n
   }<\/pre>\n
<\/div>\n<\/div>\n
At this point I can simply write $data to the pipeline. But the CMD DIR has two other parameters I like to use \/bare and \/owner.\u00a0 The former displays the full filename and path and nothing else.<\/p>\n
\n
\n
#if $bare write out only the full filename<\/span><\/pre>\n
<\/p>\n
     if<\/span> ($Bare) {<\/pre>\n
<\/p>\n
       Write-Verbose \"Writing data in bare mode\"<\/span><\/pre>\n
<\/p>\n
       $data | select FullName<\/pre>\n
<\/p>\n
     }<\/pre>\n
<\/div>\n<\/div>\n
The latter is only slightly more involved.\u00a0 I can get the owner information for each file or folder object using Get-ACL<\/a> and adding a new property with Add-Member<\/a>.<\/p>\n
\n
\n
#add owner information<\/span><\/pre>\n
<\/p>\n
$data | foreach<\/span> {<\/pre>\n
<\/p>\n
   $_ | Add-Member -MemberType NoteProperty -Name \"Owner\"<\/span> -value ((Get-ACL $_.fullname).Owner ) -passthru<\/pre>\n
<\/p>\n
}<\/pre>\n
<\/div>\n<\/div>\n
If I write $data to the pipeline, you woiuldn\u2019t see this information, unless you asked for it:<\/p>\n
PS C:\\> pdir c:\\files \u2013owner | Sort Owner | select Fullname,Length,Owner<\/span><\/p>\n
But that seemed like a lot of extra work and something you\u2019d have to remember to do. My solution was to create a custom format extension for files and folders that automatically would display the Owner. The file pdir.FileSystem.format.ps1xml is expected to be found in your PowerShell profile directory.<\/p>\n
\n
\n
#define the path to the custom format file<\/span><\/pre>\n
<\/p>\n
$profileDir=Split-Path $profile<\/pre>\n
<\/p>\n
$formatfile=\"$profiledir\\pdir.FileSystem.format.ps1xml\"<\/span><\/pre>\n
<\/div>\n<\/div>\n
This file will temporarily replace the default formatting by prepending with the custom formatting using Update-FormatData<\/a>.<\/p>\n
\n
\n
elseif<\/span> ($owner) {<\/pre>\n
<\/p>\n
        Write-Verbose \"Writing data with owner information\"<\/span><\/pre>\n
<\/p>\n
        Write-Verbose \"Loading custom format File $formatfile\"<\/span><\/pre>\n
<\/p>\n
<\/p>\n
        Update-FormatData -prepend $formatfile -ea \"SilentlyContinue\"<\/span><\/pre>\n
<\/div>\n<\/div>\n
\"captured_Image.png[8]\"<\/a><\/p>\n
But don\u2019t worry, the function reloads the originally formatting directives.<\/p>\n
\n
\n
#reload original FileSystemFormat<\/span><\/pre>\n
<\/p>\n
       Write-Verbose \"Reloading $pshome\\filesystem.format.ps1xml\"<\/span><\/pre>\n
<\/p>\n
       Update-FormatData -prepend $pshome\\filesystem.format.ps1xml -ea \"SilentlyContinue\"<\/span><\/pre>\n
<\/div>\n<\/div>\n
One thing to be aware of is that if pipe owner information to another cmdlet, the original formatting will be used so you are back to needing to specify the Owner information.<\/p>\n
\"captured_Image.png[10]\"<\/a><\/p>\n
After you install the script and PS1XML file, be sure to look at the help examples.<\/p>\n
After you download the zip file<\/a> with the script and ps1xml files, be sure to look at the README file. Enjoy and as always I hope you'll let me know what you think.<\/p>\n","protected":false},"excerpt":{"rendered":"
Some of you know my relationship with the a command prompt goes back a long, long way. Naturally I became very adept at using the DIR command, fully taking advantage of its switches to tease out hidden information or to quickly get just the information I wanted. When PowerShell first came out, I made the…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[72,75,8],"tags":[139,97,32,137,534,140,540,138],"class_list":["post-510","post","type-post","status-publish","format-standard","hentry","category-commandline","category-powershell-v2-0","category-scripting","tag-add-member","tag-filesystem","tag-functions","tag-get-childitem","tag-powershell","tag-ps1xml","tag-scripting","tag-update-formatdate"],"yoast_head":"\nAll Hail Dir UseALot! • The Lonely Administrator<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"All Hail Dir UseALot! • The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Some of you know my relationship with the a command prompt goes back a long, long way. Naturally I became very adept at using the DIR command, fully taking advantage of its switches to tease out hidden information or to quickly get just the information I wanted. When PowerShell first came out, I made the...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2009-11-16T16:30:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2009-11-16T16:39:24+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2009\/11\/captured_Image.png_thumb.png\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"All Hail Dir UseALot!\",\"datePublished\":\"2009-11-16T16:30:24+00:00\",\"dateModified\":\"2009-11-16T16:39:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/\"},\"wordCount\":836,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2009\\\/11\\\/captured_Image.png_thumb.png\",\"keywords\":[\"Add-Member\",\"FileSystem\",\"functions\",\"Get-ChildItem\",\"PowerShell\",\"ps1xml\",\"Scripting\",\"Update-FormatDate\"],\"articleSection\":[\"CommandLine\",\"PowerShell v2.0\",\"Scripting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/\",\"name\":\"All Hail Dir UseALot! • The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2009\\\/11\\\/captured_Image.png_thumb.png\",\"datePublished\":\"2009-11-16T16:30:24+00:00\",\"dateModified\":\"2009-11-16T16:39:24+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2009\\\/11\\\/captured_Image.png_thumb.png\",\"contentUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2009\\\/11\\\/captured_Image.png_thumb.png\",\"width\":\"484\",\"height\":\"226\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/510\\\/all-hail-dir-usealot\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"CommandLine\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/commandline\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"All Hail Dir UseALot!\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"All Hail Dir UseALot! • The Lonely Administrator","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/","og_locale":"en_US","og_type":"article","og_title":"All Hail Dir UseALot! • The Lonely Administrator","og_description":"Some of you know my relationship with the a command prompt goes back a long, long way. Naturally I became very adept at using the DIR command, fully taking advantage of its switches to tease out hidden information or to quickly get just the information I wanted. When PowerShell first came out, I made the...","og_url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/","og_site_name":"The Lonely Administrator","article_published_time":"2009-11-16T16:30:24+00:00","article_modified_time":"2009-11-16T16:39:24+00:00","og_image":[{"url":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2009\/11\/captured_Image.png_thumb.png","type":"","width":"","height":""}],"author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"All Hail Dir UseALot!","datePublished":"2009-11-16T16:30:24+00:00","dateModified":"2009-11-16T16:39:24+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/"},"wordCount":836,"commentCount":1,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#primaryimage"},"thumbnailUrl":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2009\/11\/captured_Image.png_thumb.png","keywords":["Add-Member","FileSystem","functions","Get-ChildItem","PowerShell","ps1xml","Scripting","Update-FormatDate"],"articleSection":["CommandLine","PowerShell v2.0","Scripting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/","url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/","name":"All Hail Dir UseALot! • The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#primaryimage"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#primaryimage"},"thumbnailUrl":"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2009\/11\/captured_Image.png_thumb.png","datePublished":"2009-11-16T16:30:24+00:00","dateModified":"2009-11-16T16:39:24+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#primaryimage","url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2009\/11\/captured_Image.png_thumb.png","contentUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2009\/11\/captured_Image.png_thumb.png","width":"484","height":"226"},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/510\/all-hail-dir-usealot\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"CommandLine","item":"https:\/\/jdhitsolutions.com\/blog\/category\/commandline\/"},{"@type":"ListItem","position":2,"name":"All Hail Dir UseALot!"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":579,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/579\/powershell-picasso\/","url_meta":{"origin":510,"position":0},"title":"PowerShell Picasso","author":"Jeffery Hicks","date":"February 23, 2010","format":false,"excerpt":"You have probably heard the story (or legend) about Pablo Picasso and his napkin drawing. A guy goes up to Picasso in a cafe and asks for an autograph or something. Picasso sketches out something in a minute or so. He turns to the guy and says, \u201cThat will be\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"powershell--picasso","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/02\/powershellpicasso_thumb.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1677,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1677\/renaming-files-with-powershell\/","url_meta":{"origin":510,"position":1},"title":"Renaming Files with PowerShell","author":"Jeffery Hicks","date":"October 12, 2011","format":false,"excerpt":"I am not a big fan of file names with spaces. I realize they are easy to read and obviously much more \"natural\", but they are simply a royal pain to deal with, especially when working from a command prompt or PowerShell. So naturally the solution is to rename these\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":475,"url":"https:\/\/jdhitsolutions.com\/blog\/mvp\/475\/pmodem-and-folder-listings\/","url_meta":{"origin":510,"position":2},"title":"PModem and Folder Listings","author":"Jeffery Hicks","date":"November 4, 2009","format":false,"excerpt":"PowerShell MVP Oisin Grehan posted a very promising PowerShell module the other day. He calls it the PModem File Transfer Protocol. It is based on the old bulletin board file transfer protocols of the late 20th century, which I have to admit I fondly remember using. Of course Oisin\u2019s work\u2026","rel":"","context":"In "CommandLine"","block_context":{"text":"CommandLine","link":"https:\/\/jdhitsolutions.com\/blog\/category\/commandline\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2144,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/2144\/have-your-output-and-variable-too\/","url_meta":{"origin":510,"position":3},"title":"Have Your Output and Variable Too","author":"Jeffery Hicks","date":"March 29, 2012","format":false,"excerpt":"There's a relatively useful suggestion floating around on Twitter on how to save results of PowerShell command to a variable and see the results at the same time. PS C:\\> ($data=get-process) I'll admit this is a clever technique: you get the results from Get-Process written to the pipeline AND a\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4707,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/4707\/a-better-powershell-more\/","url_meta":{"origin":510,"position":4},"title":"A Better PowerShell More","author":"Jeffery Hicks","date":"December 23, 2015","format":false,"excerpt":"In PowerShell, when I have a lot of output, I can use the legacy more.com command to page the results to the screen. Get-Process | more There's not anything inherently wrong with this approach. Although one drawback is that it doesn't work in the PowerShell ISE. For that reason alone\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"More PowerShell Output","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2015\/12\/image_thumb-6.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2015\/12\/image_thumb-6.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2015\/12\/image_thumb-6.png?resize=525%2C300 1.5x"},"classes":[]},{"id":2211,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/2211\/powershell-scripting-with-validatepattern\/","url_meta":{"origin":510,"position":5},"title":"PowerShell Scripting with [ValidatePattern]","author":"Jeffery Hicks","date":"April 19, 2012","format":false,"excerpt":"I've been writing about a number of parameters attributes you can include in your PowerShell scripting to validate parameter values. Today I want to cover using a regular expression pattern to validate a parameter value. I'm going to assume you have a rudimentary knowledge of how to use regular expressions\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2012\/04\/squarepattern-150x150.png?resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=510"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/510\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=510"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=510"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}