Dongbo Wang

@iSazonov I haven't yet got a chance to understand the root cause. Will try taking a look next week.

Labelled both this PR and the issue with `WG-Interactive-Console`, as the main disagreement in the discussions in #16658 is about a subtle change in tab completion for this parameter when...

> Proposed solution is to create a new `Set-StrictMode -Version 4.0` to avoid any breaking changes. This won't prevent the breaking change, because most of time, a user will use...

> EventSource.CreateManifestAndDescriptors() I don't know if it's possible to remove this delay. You see this because PerfView is collecting ETW tracing. When ETW is not collected, which is the case...

>> I'd prefer if runspace affinity was just removed from classes but I understand it's next to impossible to know the impact of a change like that. >Has anyone ever...

The `Console.Key` re-write work (https://github.com/dotnet/runtime/pull/72193) was checked in .NET on 8/1 and will be included in the RC1 release. This issue is likely to be addressed by that change. Please...

It looks `.` is used as a separator when tokenizing text like a parameter (e.g. -xxx) ``` PS:24> function bar { param($param) $param } PS:25> bar -param.abcdef .abcdef ``` Another...

VSCode integrated console and PowerShell notebook use different hosts, which haven't been updated to work with `$PSStyle`. Can you maybe open separate issues in .NET Interactive and PSES repos about...

Quote the discussion between @jhoneill and me from https://github.com/PowerShell/PowerShell/issues/16635#issuecomment-996901232 > just so I'm clear, although it's a change in PowerShell itself that caused it, the fix can only come from...

@jhoneill PowerShell integrated console started to wrap a console host instance internally. The .NET Interactive cannot wrap console host within it, because it's not facing a terminal, but the .NET...