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

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

So you remember when I said “script properties might blow up though”. Yeah turns out script properties blow up, we need to make sure we’re excluding them. Or marshal back to the pipeline thread to get the value.

I don’t think any workaround is needed in PSES since it was a change in PowerShell itself. It’s not hard to fix it there and even port it back to current LTS version.

I am

@JustinGrote You can use this method on the host to execute an arbitrary C# function within the PowerShell context:

https://github.com/PowerShell/PowerShellEditorServices/blob/149f5ac1089fef8344f8a5849a211a1ba9a88431/src/PowerShellEditorServices/Services/PowerShell/Host/PsesInternalHost.cs#L307-L314

@SeeminglyScience excluding them I can do for now, I may need help with the second part. It did blow up on “basename” which is a scriptproperty

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

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