Votes from Connect: 18

Original Date Submitted: 9/23/2011 7:23:48 PM

Description:
Contact Information
Handle: Steve Murawski
Site Name: PowerShell
Feedback ID: 690427

Frequency: Always Happens
Regression: No, this is new to the most recent version

Problem Description:
The new Where-Object syntax does not properly evaluate calling a method on a property that returns a Boolean.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 690427 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=690427).

Repro Steps:
This will error:
Get-Command | ? parameters.containskey('Credential') | sort name

This will not:
Get-Command | ? {$_.parameters.containskey('Credential')} | sort name

Expected Results:
Both commands should list out any commands that have a -Credential parameter. The first command will throw this error:
here-Object : An operator is required to compare the two specified values. Include a valid operator and retry.
t line:1 char:15
Get-Command | ? parameters.containskey('Credential') | sort name

           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

• CategoryInfo : InvalidArgument: (:) [Where-Object], PSArgumentException


• FullyQualifiedErrorId : OperatorNotSpecified,Microsoft.PowerShell.Commands.WhereObjectCommand

Internal BugId: 3047

Votes from Connect: 41

Original Date Submitted: 9/8/2011 8:47:16 PM

Description:

Contact Information
Handle: HalR
Site Name: PowerShell
Feedback ID: 687640

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
Something similar to the Get-Parameter function published on PoshCode (see http://poshcode.org/?lang=&q=get-parameter for latest version) needs to be included in PowerShell. The purpose of Get-Parameter is to parse the output of a cmdlet or function's CommandInfo returned from Get-Command, and turn it into a more useful format by which the end user can discover more about:
- what paraemtersets exist?
- what triggers a parameterset? (i.e. which are mandatory)
- what pipeline input does a cmdlet/function accept?

And more. Some of these are questions that you can discern from the help file only after reading pages and pages of data (Get-Help -Full) and basically doing much more work in your head than is necessary. Some of these questions cannot be adequately answered in the help at all and must be discovered by experimentation if the help author omitted input type data.

The answers are all in the paraameterset data. IMHO the Get-Parameter function is more useful than Get-Help because while you will refer to the help the first few times when using a new cmdlet, once you have the basics down, Get-Parameter is a more quickly digested tool and something that you will end up using on a daily basis.

More details can be found on this blog post: http://halr9000.com/article/507

P.S. I like 'gpm' as a built-in alias.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 687640 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=687640).

Repro Steps:
Expected Results:
Love this:

PS > gpm Get-EventLog

ParameterSet: LogName

Name Type IsMandatory Pipeline

LogName String True False
ComputerName String[] False False
Newest Int32 False False
InstanceId Int64[] False False
Index Int32[] False False
EntryType String[] False False
Source String[] False False
Message String False False
AsBaseObject SwitchParameter False False

ParameterSet: List

Name Type IsMandatory Pipeline

ComputerName String[] False False
List SwitchParameter False False
AsString SwitchParameter False False

Internal BugId: 3010

Votes from Connect: 56

Original Date Submitted: 4/12/2011 2:47:03 PM

Description:
Contact Information
Handle: Shay Levi
Site Name: PowerShell
Feedback ID: 659747

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
PowerShell has an automatic variable, $pwd. One of its great usage is that its value is evaluated each time you call it and you can access its members without enclosing it in parenthesis.

I would like to suggest a new automatic variable (tied variable), $Now, that returns the current date and time each time it's called.

Having $Now as a new automatic variable in PowerShell can save us extra typing, prevent enclosing get-date in parenthesis (when we need to access its members) and even save us a variable assignment to hold the current date and time, it also can be used inline in cmdlet parameters value without having to create a $date variable first.

So instead of doing:

$date = (Get-Date).MemberName

We could simply do:

$Now.MemberName

There's a post blog on the PowerShell team blog, by Ibrahim Abdul Rahim (http://blogs.msdn.com/b/powershell/archive/2009/03/26/tied-variables-in-powershell.aspx), that explains how to do it, and also an extended version by Lee Holmes (http://www.leeholmes.com/blog/2009/03/26/more-tied-variables-in-powershell)

Product Studio item created by Connect Synchronizer due to creation of feedback ID 659747 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=659747).

Repro Steps:
Expected Results:

Internal BugId: 2900

Votes from Connect: 13

Original Date Submitted: 12/27/2008 11:39:54 PM

Description:

Contact Information
Handle: tfl
Site Name: PowerShell
Feedback ID: 389767

Frequency: Always Happens
Regression: No, this is new to the most recent version

Problem Description:
I think the new auto-help stuff is fantastic. But it's a tad buggy and inconsistent.

To demonstrate this, I've created a simle advanced function file (get-autohelp.ps1) attached. You will need to save this file then run get-help against it to see the errors I note.

Here are the issues:

1. You can not specify a .NAME section in auto-help. If you do, then the output returned by get-help is heaviliy truncated. You should enable the developer to specify a name section, with Get-Help then supplementing this with the file name that the script lived in.




2. Two sections change name from script file to output by Get-Help. The ".DESCRIPTIION" section becomes "Detailed Description" in get-help output. And .LINK befomes "RELATED LINKS. This is inconsistent. Either make Get-Help produce the section names in the file, or change what sections you can specify in the file to match what get-help produces.




3. .LINK links are shown in basic get-help output, and with -FULL, but not -Detailed. This is inconsistent - anything shown in basic output should be shown with -full or -detailed.




4. It's not clear how to use .COMPONENT, .ROLE and .FUNCTIONALITY sections. These do not appear to be output in any use of get-help. If nothing else, there needs to be more details on these sections.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 389767 (http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=99&FeedbackID=389767).

Repro Steps:
1. Take Get-AutoHelp.ps1 from bug report and save it.
2. To see issue 1, add a section:
.NAME

FOO

before line 2 in attached script. Run Get-Help, Get-Help -full, Get-Help -Detailed against the script, then do it again with these lines removed.

1. Run Get-Help, Get-Help -full, Get-Help-Detailed to see the first three issues.




2. Run get-help -role *, get-help-component * to see issue

Expected Results:
1. Ability to specify a name
2. Consistency of section names to get-help output
3. Ability to use .COMPONENT, .ROLE, and .FUNCTIONALITY sections

Internal BugId: 1838