Yes, it is time to get Microsoft to clarify that issue.
On 4/5/2010 11:37 PM, Clint B wrote:
> I remember having issues with remove-item -recurse in v1, but directly
> from get-help remove-item in v2:
> "The Recurse parameter in this cmdlet does not work properly."
> C:\PS>get-childitem * -include *.csv -recurse | remove-item
> Because the Recurse parameter in this cmdlet is faulty, the command uses
> the Get-Childitem cmdlet to get the desired files, and it uses the
> pipeline operator to pass them to the Remove-Item cmdlet.
> and yet this filed bug:
> is closed "As by Design"?
> Hard to imagine that broken is genuinely by design. Do we need to reopen
> a connect issue for this?