Home Dashboard Directory Help
Search

TFS Power Tools: PowerShell cmdlets behaviour with Get-Help cmdlet by Sherif Talaat


Status: 

Active


4
0
Sign in
to vote
Type: Bug
ID: 816092
Opened: 1/29/2014 5:08:07 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

PowerShell comes with a super powerful and unique help mechanism. It provides information beyond the traditional help system that shows only the command and its parameters. Help in PowerShell is enough to know everything about what you are looking for without even going to internet and search for it; it gives you a synopsis, detailed description, syntax, parameters, input and output objects, notes, examples, and more. unfortunately, Power Tools PowerShell cmdlets are not leveraging this help capabilities and still following the traditional cmd.exe style. For example, using Get-Help cmdlet with any of Power Tools cmdlets return just the cmdlet's name and its Syntax. I believe there is big room for improvement at least add some text information to synopsis, description, and examples. Thus, I can relay on the Get-Help (as usual) to get what I need to know about the cmdlet and also code samples to help me getting started with this specific cmdlet.
This is very import issue especially because of the lack of Power Tools' cmdlets examples and code samples on both Microsoft official channel and other developers community. This is might be a reason behind the slow adoption of Power Tools' PowerShell cmdlets.
Details
Sign in to post a comment.
Posted by Microsoft on 2/6/2014 at 2:13 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.
Posted by Microsoft on 1/29/2014 at 5:53 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.