Justin Grote

Just came across this with the MSTerminalSettings 2.0. Is there a workaround perhaps, or am I going to have to develop my own? EDIT: I think this is blocked on...

If I have time I can attempt a sufficient workaround that I POC'd: 1. Use AST to strip all the comments (I have ready-to-go code for this from my module...

@jdhitsolutions It literally does this: 1. Gets the module 2. Pulls the commands from the module 3. loops through and runs get-help on each module command 4. Converts the resultant...

I will PR this if @proxb is still accepting.

At the very least, just allow the option to expose the TelemetryClient as a powershell variable, then we can call it directly to write whatever custom logs we want, in...

### Workaround Turns out the TelemetryClient works just fine inside the powershell worker: ```powershell using namespace Microsoft.ApplicationInsights function Write-Critical ([String]$message) { $tc = [TelemetryClient]::New($env:APPINSIGHTS_INSTRUMENTATIONKEY) $tc.TrackTrace($message,4, $null) } Write-Critical 'My New...

As far as the native integration, I agree that using Write-Information tags makes the most sense to keep it "Powershell-y" If I do write information with a tag, it should...

@cveld Pretty much what you did (use your own telemetry client) was going to be my suggestion.

It seems to me trying to use any of the native c# stuff would be difficult, instead I would follow the PSES/VSCode Powershell Extension's lead and use the powershell host...

#284 would be ideal, but updating Push-Output Binding in spaellings way would at least provide a workable method to get around some Table API issues without having to resort to...