René's URL Explorer Experiment

Title: Add `pwshw` for console-less PowerShell on Windows by SteveL-MSFT · Pull Request #10962 · PowerShell/PowerShell · GitHub

Open Graph Title: Add `pwshw` for console-less PowerShell on Windows by SteveL-MSFT · Pull Request #10962 · PowerShell/PowerShell

X Title: Add `pwshw` for console-less PowerShell on Windows by SteveL-MSFT · Pull Request #10962 · PowerShell/PowerShell

Description: PR Summary .NET Core 3.0 supports building WinExe type which doesn't bind to console host. This means that pwshw.exe launches like any GUI app (think notepad) and stdin/stdout/stderr isn't bound to pwshw.exe from wherever it is started. This is conceptually equivalent to the old wscript.exe and cscript.exe tools. Build script updated to also build a new powershell-win-core-w project as we still need the console pwsh.exe built. The resulting pwshw.exe and other necessary files are copied to the pwsh.exe folder. This is exposed as an experimental feature although it can't be disabled as it's a binary file. pwshw is never attached a console, so -OutputLog is added to the host to write output to a file making it easier to trouble issues. pwshw is always non-interactive even if the -interactive switch is used. ConsoleHost UserInterfaces updated to write to OutputLog if set. Code paths that try to access ActiveScreenBuffer have try...catch to fail silently when there is no console. Tests updated to account for being run within pwshw where necessary. Tests using pwsh and expecting console output is left as-is. CI is updated to run all CI and Other tests both elevated and unelevated under this new host on Windows. NOTE: scripts that call console APIs will fail as those APIs will throw that there is no console PR Context Fix #3028 PR Checklist PR has a meaningful title Use the present tense and imperative mood when describing your changes Summarized changes Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header This PR is ready to merge and is not Work in Progress. If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready. Breaking changes None OR Experimental feature(s) needed Experimental feature name(s): PSConsoleLessHost User-facing changes Not Applicable OR Documentation needed Issue filed: MicrosoftDocs/PowerShell-Docs#5039 Testing - New and feature N/A or can only be tested interactively OR Make sure you've added a new test if existing tests do not effectively test the code changed Tooling I have considered the user experience from a tooling perspective and don't believe tooling will be impacted. OR I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include: Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host). Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features. Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions). Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Open Graph Description: PR Summary .NET Core 3.0 supports building WinExe type which doesn't bind to console host. This means that pwshw.exe launches like any GUI app (think notepad) and stdin/stdout/stderr isn't...

X Description: PR Summary .NET Core 3.0 supports building WinExe type which doesn't bind to console host. This means that pwshw.exe launches like any GUI app (think notepad) and stdin/stdout/stderr isn&a...

Opengraph URL: https://github.com/PowerShell/PowerShell/pull/10962

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width