Andy Jordan

@peetrike Can you please clarify: do you have these projects marked "trusted" or "untrusted"? I have to assume "trusted" or the extension wouldn't/shouldn't be starting in the first place at...

Sounds like the changes made upstream to VS Code isn't allowing for spawned processes to be closed :/

@TylerLeonhardt is this something VS Code could look at?

I wonder if this is related to https://github.com/PowerShell/vscode-powershell/issues/3360, so when we fix that bug, let's test this again.

@Tyriar Hey, just FYI, I see this same bug exist with the C# extension where the spawned `dotnet` processes aren't closed. I'm frequently having to go to my activity manager...

@peetrike with the PR Tyriar mentioned and the latest version of VS Code, there's a good chance this has been fixed. Can you try the the latest [PowerShell Preview for...

Hey, that's a good find and will help us narrow it down.

@SeeminglyScience any idea here? My instinct says it's acting like there's an issue with the multi-line startup banner string, as that's the only thing with the word "Extension" in it.

Hi there, I can take a look at disabling the startup banner if we detect that we're using this `dotnet` install of PowerShell. Meanwhile, you can simply disable the startup...

Unfortunately we don't currently have extensive tests for Constrained Language Mode compatibility, so while this feature was at one point implemented, we have no way to guarantee that it will...