Batch to Powershell: dir /s

I often go looking for a file in batch, aka 

c:\Program Files (x86)>dir /s fsi*
     Volume in drive C has no label.
     Volume Serial Number is 8EDE-D64E

     Directory of c:\Program Files (x86)\Microsoft F#\v4.0

    03/19/2010  02:02 PM           230,216 Fsi.exe
    09/30/2009  08:08 PM               158 Fsi.exe.config
                   2 File(s)        230,374 bytes
Unfortunately this doesn't 'just work' in powershell. A quick search on the internet shows in powershell 'dir /s' becomes 'dir -r', but the following doesn't work either: 
PS C:\Program Files (x86)> dir -r fsi*
PS C:\Program Files (x86)>
What's going on? Let's check the help: 
PS C:\Program Files (x86)> help dir

NAME
    Get-ChildItem

SYNOPSIS
    Gets the items and child items in one or more specified locations.


SYNTAX
    Get-ChildItem [[-Path] ] [[-Filter] ] [-Exclude ] [-For
    ce] [-Include ] [-Name] [-Recurse] [-UseTransaction] []

    Get-ChildItem [-LiteralPath]  [[-Filter] ] [-Exclude ]
    [-Force] [-Include ] [-Name] [-Recurse] [-UseTransaction] []

Ahh, path and filter are two separate arguments in powershell. This means we get 2 choices.

A) Pass a path to the dir command (pass ‘.’ for current directory): 

PS C:\Program Files (x86)> dir . fsi* -r

    Directory: C:\Program Files (x86)\Microsoft F#\v4.0


Mode                LastWriteTime     Length Name
----                -------------     ------ ----
-a---         3/19/2010   2:02 PM     230216 Fsi.exe
-a---         9/30/2009   8:08 PM        158 Fsi.exe.config
PS C:\Program Files (x86)>
B) Explicitly pass the -filter argument name (which we can abbreviate to -fi) 
PS C:\Program Files (x86)> dir -r -fi fsi*


    Directory: C:\Program Files (x86)\Microsoft F#\v4.0


Mode                LastWriteTime     Length Name
----                -------------     ------ ----
-a---         3/19/2010   2:02 PM     230216 Fsi.exe
-a---         9/30/2009   8:08 PM        158 Fsi.exe.config    
PS C:\Program Files (x86)>

OK you’re thinking who cares, I can still do dir /s faster in batch? Ah, but you can’t do this:

 PS C:\Program Files (x86)> dir -r -fi fsi* | Where-Object {$_.Length -gt 200KB}


    Directory: C:\Program Files (x86)\Microsoft F#\v4.0


Mode                LastWriteTime     Length Name
----                -------------     ------ ----
-a---         3/19/2010   2:02 PM     230216 Fsi.exe
PS C:\Program Files (x86)>

Have fun, and remember read the docs when things don’t work as you’d expecxt:)

Comments

Sriram Krishnan said…
This annoys me in PS everytime. I have too much muscle memory to unlearn 'dir /s' :)
8/01/2010 12:06 PM
Post a Comment

Popular posts from this blog

Finding CLR exceptions without visual studio

(If you want to understand what exception code 0xe0434352 is, read this post ) Often exceptions are thrown and caught and you don't see them. You probably know how to debug this in Visual Studio, so let me show you how to do it in cdb. Sample Code: class Program { static void Main(string[] args) { foreach (var x in Enumerable.Range(0,2000)) { Thread.Sleep(TimeSpan.FromSeconds(1)); Console.WriteLine("Hello World"); ThrowAndCatchException(); } } private static void ThrowAndCatchException() { try { throw new NotImplementedException(); } catch(Exception) { } } } Output of the application: Hello World Hello World Hello World Nothing about an exception, but you're sure it's happening behind the covers -- fire up cdb: C:\Program Files\Debugging Tools for Windows (x64)>cdb -pn consoleapplication3.exe <SNIP> ModLoad: 000007fe`f7e90000 000007fe`f7eb4000 C:\Windows\Mi
Read more

Why do I keep getting exception code e0434352?

If you want to know how to debug CLR exceptions using cdb then read this post . Exception code e0434352 is the exception code used internally by the CLR to represent most exceptions(*). Regardless of if you throw a System.NullReferenceException or a System.ArgumentException in C#, you'll throw a SEH exception e0434352 under the covers. A fun way to validate this theory is to watch what happens to the CLR exceptions settings in cdb. Fire up cdb, and see the state of clr exceptions: 0:000> .shell -ci "sx" findstr clr clr - CLR exception - second-chance break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Now, set the exception handler for exception number e0434352 and recheck the value of the clr exception handler: 0:000> sxe e0434352 0:000> .shell -ci "sx" findstr clr clr - CLR exception - break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Armed with
Read more

Powershell script to enable windows to capture localhost traffic in wireshark

If you want to understand why the following scripts work read this post . Otherwise just paste the following into an elevated powershell window: Setup windows networking to allow localhost capturing in wireshark: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "You don't have 1 default gateway, your network configuration is not supported" } # Route local IP address via the default gateway route add $defaultAdapter.IPAddress[0] $defaultAdapter.DefaultIPGateway Write-Host "Start capturing on localhost by connecting to $($defaultAdapter.IPAddress[0])" Return windows networking to normal configuration: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "Y
Read more