Votes from Connect: 28

Original Date Submitted: 6/26/2012 10:32:58 PM

Description:
Contact Information
Handle: Trevor Sullivan
Site Name: PowerShell
Feedback ID: 750939

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

Problem Description:
The Windows PowerShell ISE does not currently display .NET object constructor signatures. When instantiating .NET objects using the New-Object cmdlet, along with its -TypeName and -ArgumentList parameters, it would be a great workflow enhancement to have the ISE's Intellisense display the object constructor signatures, such that a developer does not have to resort to pulling up the MSDN documentation online much less frequently. Memorizing object constructor signatures can be challenging for .NET types that are not often used, or for new developers who are exploring an unfamiliar .NET type.

For bonus points, it would be awesome to have the ISE resolve & display a clickable link that would take a developer directly to the MSDN documentation for the .NET type name that is specified in the -TypeName parameter, assuming that it is part of the Microsoft .NET Base Class Library (BCL). Obviously, for 3rd party .NET assemblies, this may be more challenging, although it may still be extractable from assembly metadata.

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

Repro Steps:
Type the following command into the ISE, and observe that it does not display any Intellisense for the .NET object constructor:

New-Object -TypeName System.IO.MemoryStream -ArgumentList

Expected Results:
Once the -ArgumentList parameter has been specified (after the -TypeName parameter has already been specified), the PowerShell ISE's Intellisense feature should be intelligent enough to pick up that the developer desires to use one of the object constructors for the System.IO.MemoryStream, and should display the available constructor signatures.

Internal BugId: 3674