René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Invoke-RestMethod parameter combination of OutFile/PassThru does not write to file as intended","articleBody":"## Problem description\r\n\r\nIn `Invoke-RestMethod`, the **PassThru** parameter must be used with the **OutFile** parameter. The intent is that you can write the results to the file and get the output to the pipeline. But the cmdlets only write to the pipeline, not the file.\r\n\r\nThe problem code starts here:\r\n\r\nhttps://github.com/PowerShell/PowerShell/blob/38d582f038f31acfc1a748d60a5331eb82a3bd28/src/Microsoft.PowerShell.Commands.Utility/commands/utility/WebCmdlet/Common/InvokeRestMethodCommand.Common.cs#L387\r\n\r\n```csharp\r\nif (ShouldWriteToPipeline)\r\n{\r\n   ...\r\n}\r\nelse if (ShouldSaveToOutFile)\r\n{\r\n   ...\r\n}\r\n```\r\n\r\nNotice that the logic outputs pipeline and skips the output to the file. Both `ShouldWriteToPipeline` and `ShouldSaveToOutFile` can be true so need to remove the `else`.\r\n\r\n## Steps to reproduce\r\n\r\n```powershell\r\nInvoke-RestMethod https://taxonomyservice.azurefd.net/taxonomies/product-uri -PassThru -OutFile C:\\temp\\irm.json\r\n```\r\n\r\n## Expected behavior\r\n\r\nOutput to console and to the file.\r\n\r\n## Actual behavior\r\n\r\nOutput to console only. The output file is not created.\r\n\r\n## Environment data\r\n\r\nThis affects all versions 5.1 and higher.\r\n\r\n","author":{"url":"https://github.com/sdwheeler","@type":"Person","name":"sdwheeler"},"datePublished":"2021-05-14T21:53:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":20},"url":"https://github.com/15409/PowerShell/issues/15409"}