Regression: Most of FileInfo object properties is missing in debug view

[kborowinski]

Most of FileInfo object properties is missing in debug view comparing to latest stable release of VSC for PowerShell (v2021.10.2)

Only small set of properties is visible:

#inculded in view:

PSPath
PSParentPath
PSChildName
PSDrive
PSProvider
PSIsContainer
Mode

#not included:

VersionInfo
BaseName
Target
LinkType
Name
Length
DirectoryName
Directory
IsReadOnly
Exists
FullName
Extension
CreationTime
CreationTimeUtc
LastAccessTime
LastAccessTimeUtc
LastWriteTime
LastWriteTimeUtc
Attributes

Latest preview version of VSC for PowerShell (v2021.12.0):

VS

Latest stable version of VSC for PowerShell (v2021.10.2):

[JustinGrote]

As @SeeminglyScience noted in a discussion, it looks like only non-NoteProperties are missing:

[JustinGrote]

I was able to reproduce this, on 7.2 some codeproperties also show up. Hmm...

[dkattan]

Could this potentially be related to: PowerShell/PowerShell#10759

the tl;dr of that issue is that Windows PowerShell serializes these properties on FileInfo objects with their correct name while PowerShell 6+ expects the property names to be like NameString, LastUpdatedString, etc.

That issue has gotten some traction recently since I got to the bottom of the propertyname mismatch.

Do the properties appear if you do:

$item = Get-ChildItem "C:\Windows\WindowsUpdate.log" | ft
$item.PSObject.Properties.Name

Does it only happen on Windows PowerShell?

[JustinGrote]

@dkattan this test was on 7.2.1, I got the additional codeproperty objects but the core property objects don't show. That issue is more around format display of serialized objects, which might be related here. Haven't had time to fully dig into it yet.

[kborowinski]

@dkattan I don't think it is related at all. I don't serialize the Get-ChildItem output (I don't pipe to Format-Table) and I get full property list on PowerShell 7.2 and PowerShell 5.1:

PowerShell 7.2:

PowerShell 5.1:

And when I rollback the PowerShell extension for VSC to latest stable version (2021.10.2 that is) I see all properties in the debug view regardless if I run on PS 7.2 or PS 5.1. I think that it's related to recent changes in how PowerShell extension for VSC populates variables in the debug view.

BTW: Format-Table from your example stripes all the FileInfo object properties obviously.

[JustinGrote]

I didn't mean to imply it was a PS issue, I agree it's probably due to recent var changes, because we unified the code paths for both serialized and non-serialized objects and there's probably something in the reflection that is screwy.

[kborowinski]

@JustinGrote We are in agreement then 😉

@dkattan To add to my previous comment, bellow you have debug view from VSC with latest stable PowerShell extension (2021.10.2) running PowerShell 7.2 and PowerShell 5.1 and in both cases all properties are visible.

VSC 1.63.2 (stable) with PowerShell extension 2021.10.2 (stable) and PowerShell 7.2:

VSC 1.63.2 (stable) with PowerShell extension 2021.10.2 (stable) and PowerShell 5.1:

[JustinGrote]

@JustinGrote We are in agreement then 😉

@dkattan To add to my previous comment, bellow you have debug view from VSC with latest stable PowerShell extension (2021.10.2) running PowerShell 7.2 and PowerShell 5.1 and in both cases all properties are visible.

Yes this should be a decent workaround until we figure out why it's not pulling all of the properties

[JustinGrote]

Looks like for FileInfo objects specifically a GetValueInvocationException is getting swallowed and causing the silent failure of the remaining properties

Exception thrown: 'System.Management.Automation.GetValueInvocationException' in System.Management.Automation.dll

[JustinGrote]

@andschwa this might fall into your wheelhouse, its failing to fetch the property because a runspace isn't present

Exception has occurred: CLR/System.Management.Automation.GetValueInvocationException
Exception thrown: 'System.Management.Automation.GetValueInvocationException' in System.Management.Automation.dll: 'Exception getting "BaseName": "There is no Runspace available to run scripts in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The script block you attempted to invoke was: $this.Name"'
 Inner exceptions found, see $exception in variables window for more details.
 Innermost exception 	 System.Management.Automation.PSInvalidOperationException : There is no Runspace available to run scripts in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The script block you attempted to invoke was: $this.Name
   at System.Management.Automation.ScriptBlock.GetContextFromTLS()
   at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Boolean propagateAllExceptionsToTop, List`1 variablesToDefine, Dictionary`2 functionsToDefine, Object[] args)
   at System.Management.Automation.ScriptBlock.DoInvokeReturnAsIs(Boolean useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Object[] args)
   at System.Management.Automation.PSScriptProperty.InvokeGetter(Object scriptThis)