René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"7.4.0 Redirecting stdout and stderr to Two Separate Files Leaves Empty Files","articleBody":"### Prerequisites\n\n- [X] Write a descriptive title.\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\n- [X] Search the existing issues.\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\n\n### Steps to reproduce\n\nWhen I redirect the output and error streams of a native command to two separate files (when I know the command writes to the error stream), both files are created but they are both empty. The error file should contain content. If I redirect only the error stream, the file will contain the correct content.\r\n\r\nHere I'm using `dotnet` as an example but the same thing happens with other commands. If you run `dotnet garbage` it will write to the error stream.\r\n\r\n```\r\ndotnet \u003ex.txt 2\u003ey.txt garbage\r\n```\n\n### Expected behavior\n\n```console\nPS\u003e dotnet \u003ex.txt 2\u003ey.txt garbage\r\n                                                                                                              PS\u003e Get-Content y.txt\r\nThe command could not be loaded, possibly because:\r\n  * You intended to execute a .NET application:\r\n      The application 'garbage' does not exist.\r\n  * You intended to execute a .NET SDK command:\r\n      No .NET SDKs were found.\r\n\r\nDownload a .NET SDK:\r\nhttps://aka.ms/dotnet-download\r\n\r\nLearn about SDK resolution:\r\nhttps://aka.ms/dotnet/sdk-not-found\n```\n\n\n### Actual behavior\n\n```console\nPS\u003e dotnet \u003ex.txt 2\u003ey.txt garbage\r\n                                                                                                                                                                                 PS\u003e Get-Content y.txt\r\n                                                                                                                                                                                 PS\u003e dotnet 2\u003ey.txt garbage\r\n                                                                                                                                                                                 PS\u003e Get-Content y.txt\r\nCould not execute because the specified command or file was not found.\r\nPossible reasons for this include:\r\n  * You misspelled a built-in dotnet command.\r\n  * You intended to execute a .NET program, but dotnet-garbage does not exist.\r\n  * You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.\n```\n\n\n### Error details\n\n```console\nN/A\n```\n\n\n### Environment data\n\n```powershell\nName                           Value\r\n----                           -----\r\nPSVersion                      7.4.0\r\nPSEdition                      Core\r\nGitCommitId                    7.4.0\r\nOS                             Microsoft Windows 10.0.19044\r\nPlatform                       Win32NT\r\nPSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}\r\nPSRemotingProtocolVersion      2.3\r\nSerializationVersion           1.1.0.1\r\nWSManStackVersion              3.0\n```\n\n\n### Visuals\n\n![image](https://github.com/PowerShell/PowerShell/assets/66026737/125e9090-690e-4ef2-9260-6900f356f985)\r\n\r\n![image](https://github.com/PowerShell/PowerShell/assets/66026737/cab9e08d-4563-4d4c-ad4f-17a218c4caac)\r\n","author":{"url":"https://github.com/twinter-amosfivesix","@type":"Person","name":"twinter-amosfivesix"},"datePublished":"2023-11-21T22:31:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/20747/PowerShell/issues/20747"}