Issue #1: The Name parameter should be positional and should have position 0. (General rule of thumb, the name parameter should be this way for ALL new- cmdlets.)
PS > New-ResourcePool bob New-ResourcePool : A parameter cannot be found that matches parameter name 'bob'.
Issue #2: The Location parameter should perhaps be marked as mandatory. Doing so would prevent this ugly error message:
PS > New-ResourcePool -Name bob New-ResourcePool : Exception has been thrown by the target of an invocation.
There's a doc bug in the help, but I'll contact the tech writer directly.
Author of the upcoming book: Managing VMware Infrastructure with PowerShell
Co-Host, PowerScripting Podcast (http://powerscripting.net)
Hi,
10x for informing us about the problems.
Issue#1: Yes there are few New-* cmdlets that are not consistent about the position of the Name parameter and I'll raise this issue
Issue#2: This is a bug. Such error messages should not be visible for the users.
Yavor
Hi,
10x for informing us about the problems.
Issue#1: Yes there are few New-* cmdlets that are not consistent about the position of the Name parameter and I'll raise this issue
Issue#2: This is a bug. Such error messages should not be visible for the users.
Yavor