René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Directly constructed .NET type instances lack properties that ones output by cmdlets have","articleBody":"_Update_: See also this later proposal to provide the provider properties via class-backed CodeProperty members rather than per-instance NoteProperty members.\r\n\r\n * #7501\r\n \r\n---\r\n\r\nFrom what I can tell, this discrepancy has always existed, so there may be a good reason for it, but it deserves an explanation / documentation.\r\n\r\nSpecifically, where do the extra properties come from? They appear not to be part of the ETS type data as returned by `Get-TypeData System.IO.DirectoryInfo` (and there's also none for the parent type, `Get-TypeData System.IO.FileSystemInfo`).\r\n\r\nThe absence of the `.PSPath` property from the directly constructed `[System.IO.DirectoryInfo]` and `[System.IO.FileInfo]` instances  is especially problematic, because pipeline-binding to `-LiteralPath` parameters is based on it.\r\n\r\nThe types used are just an example; the same discrepancy exists for other types, such as `[datetime]::now` vs. `Get-Date`.\r\n\r\nSteps to reproduce\r\n------------------\r\n\r\n```powershell\r\n# Construct  seemingly identical [System.IO.DirectoryInfo] instances\r\n([System.IO.DirectoryInfo] '/').psextended | Format-List\r\n'---'\r\n(Get-Item '/').psextended | Format-List\r\n```\r\n\r\nExpected behavior\r\n-----------------\r\n\r\n```none\r\nPSPath        : Microsoft.PowerShell.Core\\FileSystem::/\r\nPSParentPath  : \r\nPSChildName   : \r\nPSDrive       : /\r\nPSProvider    : Microsoft.PowerShell.Core\\FileSystem\r\nPSIsContainer : True\r\nMode          : d-r---\r\nBaseName      : /\r\nTarget        : \r\nLinkType      : \r\n\r\n---\r\n\r\nPSPath        : Microsoft.PowerShell.Core\\FileSystem::/\r\nPSParentPath  : \r\nPSChildName   : \r\nPSDrive       : /\r\nPSProvider    : Microsoft.PowerShell.Core\\FileSystem\r\nPSIsContainer : True\r\nMode          : d-r---\r\nBaseName      : /\r\nTarget        : \r\nLinkType      : \r\n```\r\n\r\nActual behavior\r\n---------------\r\n\r\n```none\r\nMode     : d-r---\r\nBaseName : /\r\nTarget   : \r\nLinkType : \r\n\r\n---\r\n\r\nPSPath        : Microsoft.PowerShell.Core\\FileSystem::/\r\nPSParentPath  : \r\nPSChildName   : \r\nPSDrive       : /\r\nPSProvider    : Microsoft.PowerShell.Core\\FileSystem\r\nPSIsContainer : True\r\nMode          : d-r---\r\nBaseName      : /\r\nTarget        : \r\nLinkType      : \r\n```\r\n\r\nAs you can see, the `PS`-prefixed properties only exist on the instance output by `Get-Item`.\r\n\r\nEnvironment data\r\n----------------\r\n\r\n```powershell\r\nPowerShell Core v6.0.0-beta.4 on macOS 10.12.5\r\nPowerShell Core v6.0.0-beta.4 on Ubuntu 16.04.2 LTS\r\nPowerShell Core v6.0.0-beta.4 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)\r\nWindows PowerShell v5.1.15063.413 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2017-07-26T15:08:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":24},"url":"https://github.com/4347/PowerShell/issues/4347"}