René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"CLI: when installed as a .NET global tool (dotnet tool), argument parsing is broken","articleBody":"Note:\r\n\r\n* This problem was discovered  by @gerardog, and this issue is meant to supersede #11569\r\n\r\n* It only affects PowerShell _when installed as a .NET global tool_:\r\n  * `dotnet tool install --global PowerShell`\r\n  * Note: You need a .NET Core SDK 3.1 installation first.\r\n\r\n# Steps to reproduce\r\n\r\n```powershell\r\n# NOTE: \r\n#  * Problem shows if `pwsh` was installed via `dotnet tool --global`\r\n#  * Run from *cmd.exe* or *bash*\r\npwsh -noprofile -c \"write-output 1 \\\"2 3\\\"\"\r\n```\r\n\r\n# Expected behavior\r\n\r\n```none\r\n1\r\n2 3\r\n```\r\n\r\nThat is, the escaped embedded double quotes (`\\\"`) should be honored, resulting in two outputs, `1`, and `'2 3'`.\r\n\r\nThis is indeed what happens with a regularly installed version.\r\n\r\n# Actual behavior\r\n\r\n```none\r\n1\r\n2\r\n3\r\n```\r\n\r\nThis output suggests that the embedded escaped double quotes (`\\\"`) were unexpectedly _eaten_.\r\n\r\n# Environment data\r\n\r\n```none\r\nPowerShell Core 7.0 # as a global .NET tool, all platforms\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2020-01-31T20:59:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/11747/PowerShell/issues/11747"}