Abstract
Did you know that PowerShell has no concept of files or folders? That’s why all the operations that involve files and folders seem to be referring to items: Get-Item, Get-ChildItem, Get-ItemProperties. When I first saw that dir was actually an alias for Get-ChildItem, I screamed. I felt as if the cmdlet naming convention has been conceived by a really sick mind. But, later as I was learning more about the shell, I found out that the reasoning behind the item concept is that PowerShell works with all types of objects that look like files. Instead of taking the UNIX shells’ approach and calling everything a file, even things that are obviously not files, the language designers have come up with the item concept.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2008 Hristo Deshev
About this chapter
Cite this chapter
(2008). Providers. In: Pro Windows PowerShell. Apress. https://doi.org/10.1007/978-1-4302-0546-3_7
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0546-3_7
Publisher Name: Apress
Print ISBN: 978-1-59059-940-2
Online ISBN: 978-1-4302-0546-3
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books