PowerShell/PowerShell

Summary of the new feature / enhancement As a user of Invoke-RestMethod or Invoke-WebRequest I would like to be able to use API's that leverage the QUERY method. Proposed technical implementation details (optional) RFC10008 was approved June this year and the method exists in .NET10 and .NET11. At a minimum I believe we need to add it to WebRequestMethod.cs

Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerShell 5.1 and PowerShell. Steps to reproduce $source = @' using System.Collections.Specialized; using System.Management.Automation; [Cmdlet("Test", "StringCollectionBinding")] public sealed class TestStringCollectionBindingCommand : PSCmdlet { [Parameter(Mandatory = true)] public StringCollection Value { get; set; } protected override void ProcessRecord() { WriteObject(Value[0]); } } '@ $type = Add-Type -TypeDefinition $source -PassThru Import-Module -Assembly $type.Assembly # Select-Object emits one scalar PSObject wrapping a string. $value = 'test-value' | Select-Object -Unique $value.GetType().FullName $value -is [System.Management.Automation.PSObject] Test-StringCollectionBinding -Value $value # The control case succeeds: Test-StringCollectionBindin

Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerShell 5.1 and PowerShell. This bug relates to a variable being changed even when an error results from -Option Constant being included in the Set-Variable call. I found 3 variations of this bug. 1. Writable variable is mutated even though an error results & { New-Variable -Name x -Value 1 Set-Variable -Name x -Value 2 -Option Constant ` -ErrorVariable setError Get-Variable -Name x | Select-Object Name, Value, Options $setError.FullyQualifiedErrorId } Error Message: Set-Variable: Line | 4 | Set-Variable -Name x -Value 2 -Option Constant ` | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Existing variable x cannot be made constant. Variables can be made constant only at creation time. Expected: Name Value Options ----

Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerShell 5.1 and PowerShell. Steps to reproduce As in the title, neither -Path nor -LiteralPath is marked as mandatory for Export-Csv. This prevents the cmdlet from promting for a path if we do not provide one, even though a path is required for the cmdlet to run. PS C:\Users\xyz> (Get-Command -Name Export-Csv).ImplementingType.GetProperty('Path').GetCustomAttributes([System.Management.Automation.ParameterAttribute]) ExperimentName : ExperimentAction : None Position : 0 ParameterSetName : __AllParameterSets Mandatory : False ValueFromPipeline : False ValueFromPipelineByPropertyName : False ValueFromRemainingArguments : False HelpMessage : HelpMessageBaseName

Steps to reproduce Run the Test-Connection cmdlet specifying a buffer size of 0, then inspect the BufferSize property of the output PingStatus object, or check the returned table: $result = Test-Connection -TargetName localhost -Count 1 -BufferSize 0 Write-Host "Result BufferSize property: $($result.BufferSize)" Write-Host "Actual Reply.Buffer.Length: $($result.Reply.Buffer.Length)" Expected behavior The cmdlet output and the BufferSize property should correctly reflect the requested buffer size of 0: Result BufferSize property: 0 Actual Reply.Buffer.Length: 0 Actual behavior The cmdlet output and the BufferSize property incorrectly report 32: Result BufferSize property: 32 Actual Reply.Buffer.Length: 0 The console output table also reports the BufferSize (B) as 32: Ping Source Address Latency BufferSize Status (ms) (B) ---- ------ ------- ------- ---------- ------ 1 l