问题
I need to get all the files including the files present in the subfolders that belong to a particular type.
I am doing something like this, using Get-ChildItem:
Get-ChildItem "C:\windows\System32" -Recurse | where {$_.extension -eq ".txt"}
However, it's only returning me the files names and not the entire path.
回答1:
Add | select FullName to the end of your line above. If you need to actually do something with that afterwards, you might have to pipe it into a foreach loop, like so:
get-childitem "C:\windows\System32" -recurse | where {$_.extension -eq ".txt"} | % {
Write-Host $_.FullName
}
回答2:
This should perform much faster than using late filtering:
Get-ChildItem C:\WINDOWS\System32 -Filter *.txt -Recurse | % { $_.FullName }
回答3:
You can also use Select-Object like so:
Get-ChildItem "C:\WINDOWS\System32" *.txt -Recurse | Select-Object FullName
回答4:
Here's a shorter one:
(Get-ChildItem C:\MYDIRECTORY -Recurse).fullname > filename.txt
回答5:
If relative paths are what you want you can just use the -Name flag.
Get-ChildItem "C:\windows\System32" -Recurse -Filter *.txt -Name
回答6:
Get-ChildItem -Recurse *.txt | Format-Table FullName
That is what I used. I feel it is more understandable as it doesn't contain any loop syntax.
回答7:
Try this:
Get-ChildItem C:\windows\System32 -Include *.txt -Recurse | select -ExpandProperty FullName
回答8:
This worked for me, and produces a list of names:
$Thisfile=(get-childitem -path 10* -include '*.JPG' -recurse).fullname
I found it by using get-member -membertype properties, an incredibly useful command. most of the options it gives you are appended with a .<thing>, like fullname is here. You can stick the same command;
| get-member -membertype properties
at the end of any command to get more information on the things you can do with them and how to access those:
get-childitem -path 10* -include '*.JPG' -recurse | get-member -membertype properties
回答9:
Really annoying thing in PS 5, where $_ won't be the full path within foreach. These are the string versions of FileInfo and DirectoryInfo objects. For some reason a wildcard in the path fixes it, or use PS 6. You can also pipe to get-item in the middle.
Get-ChildItem -path C:\WINDOWS\System32\*.txt -Recurse | foreach { "$_" }
Get-ChildItem -path C:\WINDOWS\System32 -Recurse | get-item | foreach { "$_" }
回答10:
gci "C:\WINDOWS\System32" -r -include .txt | select fullname
回答11:
[alternative syntax]
For some people, directional pipe operators are not their taste, but they rather prefer chaining. See some interesting opinions on this topic shared in roslyn issue tracker: dotnet/roslyn#5445.
Based on the case and the context, one of this approach can be considered implicit (or indirect). For example, in this case using pipe against enumerable requires special token $_ (aka PowerShell's "THIS" token) might appear distasteful to some.
For such fellas, here is a more concise, straight-forward way of doing it with dot chaining:
(gci . -re -fi *.txt).FullName
(<rant> Note that PowerShell's command arguments parser accepts the partial parameter names. So in addition to -recursive; -recursiv, -recursi, -recurs, -recur, -recu, -rec and -re are accepted, but unfortunately not -r .. which is the only correct choice that makes sense with single - character (if we go by POSIXy UNIXy conventions)! </rant>)
回答12:
I am using below script to extact all folder path:
Get-ChildItem -path "C:\" -Recurse -Directory -Force -ErrorAction SilentlyContinue | Select-Object FullName | Out-File "Folder_List.csv"
Full folder path is not coming. After 113 characters, is coming:
Example - C:\ProgramData\Microsoft\Windows\DeviceMetadataCache\dmrccache\en-US\ec4d5fdd-aa12-400f-83e2-7b0ea6023eb7\Windows...
来源：https://stackoverflow.com/questions/13126175/get-full-path-of-the-files-in-powershell