Cadence

Hi @sergey-tihon I'll certainly take a shot at it. I've gotten similar errors with a few other cmdlets, and I don't have a good solution for debugging the type provider...

I've managed to learn a little more about the bug. [line 134](https://github.com/fsprojects/FSharp.Management/blob/master/src/FSharp.Management.PowerShell/HostedRuntime.fs#L134) in HostedRuntime.Execute is being triggered because - and this doesn't show up in the Get-ExecutionPolicy signature - listing...

Apparently PowerShell populates `CommandInfo.OutputType` from an attribute that goes on the cmdlet type. So there's no actual guarantee the output type will actually match the real output. It doesn't seem...

If there is another way, it might have to be a very clever fix. PS doesn't decide what kind of output you get until the last minute:  Not great...

I think the logic must've been something like the following: 1. A lot of the important logic is in the `Myriad.Sdk` MSBuild scripts. 2. If you were to `dotnet tool...