Dongbo Wang

The Engine WG reviewed this issue today. The root cause of the issue is related to how module defined classes get exposed outside of the module scope. ### Root Cause...

Closed as a duplicate of https://github.com/PowerShell/PowerShell/issues/24863

Tag the Security WG to review and suggest the next step.

@RokeJulianLockhart As shown in the screenshot below, you copied the text from the terminal output before pasting to `Get-Content -LiteralPath`. I believe when you copy the terminal output, you already...

Yes, I understand. Tab is intentionally replaced with 4 space characters (see [the code](https://github.com/PowerShell/PSReadLine/blob/eff1452a647a0bb5863cf5fa42062b3b1f701c10/PSReadLine/KillYank.cs#L675-L676)), and it was a by design change: https://github.com/PowerShell/PSReadLine/issues/144. I just want to point out that the...

Leave the "Needs-Triage" label on and @IISResetMe can bring it back to Engine WG meeting after the investigation.

Are you able to import the module in v7.2.10, v7.3.3, and the v7.4.0-preview.1 of PowerShell?

Removed the "Resolution" label. We need to keep this issue open and verify if this is caused by moving to .NET 8. /cc @adityapatwardhan @TravisEz13 @SeeminglyScience

@jborean93 Thank you so much for the investigation! The package `System.ServiceModel.Primitives` referenced in `Microsoft.PowerShell.SDK.csproj` was the version `4.x.0` previously, and became `6.0.0-preview1.23060.3` after moving to .NET 8. - In the...

I agree. Leaving it as is will break a lot of scripts. For this particular issue, I guess we will have to lock the versions of the `System.ServiceModel.xxxxx` NuGet package...