Joel Bennett

I'm concerned about this `-SkipPathValidation` parameter name and about what @iSazonov wrote: > ... GetResolvedProviderPathFromPSPath resolves glob chars vs GetUnresolvedProviderPathFromPSPath doesn't ... I believe we want GetResolvedProviderPathFromPSPath but internal one...

@BrucePay and the -ErrorVariable _must_ mirror that? I mean, I'm ok with everything being in $Error ... @SteveL-MSFT I guess that would at least give us a way ... Right...

@mklement0 I think you're confusing the use case. Are you suggesting that it's ok that an application that uses the PowerShell class to invoke scripts for automation would need to...

I think we're in agreement. My request is focused on ErrorVariable only because I was focused on error detection in a script. That is, I wasn't concerned with `PowerShell.Invoke` or...

Ok, after three days of trying ... I finally thought of searching through **all** of GitHub for use of `TargetTypeForDeserialization` and came across the solution. The TypeData needs to be...

It turns out, there's a different problem: this *does not work* for PowerShell classes. Take this simple case for example: ```posh class Test { [string]$FirstName [string]$LastName [string]$FullName Test([string]$FirstName, [string]$LastName) {...

Thanks. I'll just ... write those classes in C# I guess. But I guess we need to document that you can write C# classes and PowerShell converters but not both...

It seems like **this** is fairly straightforward and doesn't break anything that's _not already broken_. > @PowerShell/powershell-committee reviewed this and agree that throwing an error is a better experience than...

@kilasuit Once 7.5 comes out, having the latest stable as an option makes sense, and would be in line with other tools. I would think anything beyond that would be...

Good idea. I'll move this in my (bigger) PR too.