Home Dashboard Directory Help
Search

PowerShell ISE v3 RTM: Intellisense does not show up consistently by Trevor Sullivan [MVP]


Status: 

Active


23
0
Sign in
to vote
Type: Bug
ID: 772736
Opened: 11/29/2012 7:17:37 AM
Access Restriction: Public
0
Workaround(s)
view
5
User(s) can reproduce this bug

Description

NOTE: See file attachment for video demonstration of this bug.

-------------------------------------------------

Intellisense does not consistently show up for all possible options. Consider the following scenario:

You add the System.Speech assembly, and then want to reference a type in the System.Speech namespace. You might type the following code

    Add-Type -AssemblyName System.Speech; # Hit F8 to run this in ISE
    # Now type this next line out, and note how the System.Speech namespace is not
    # in the Intellisense autocomplete list.
    [System.Spee

The child namespaces and types of System.Speech are enumerated in Intellisense, but only *after* you have completed typing the word "Speech" as in: [System.Speech].
Details
Sign in to post a comment.
Posted by deadlydog on 6/20/2013 at 8:55 AM
Scratch my comment about it only being a problem in the Script Pane. Today I am having the same problem in the Console where typing $psISE.CurrentFile. does not pop the intellisense up.
Posted by deadlydog on 6/19/2013 at 9:31 AM
I too have only started using Windows PowerShell ISE v3 in the last week and have consistently noticed that the intellisense is not consistent, but only in the Script Pane; It seems to be consistent in the Console. Since I just started using ISE I've found many shortcomings and have been writing addons for it. For me the intellisense frequently doesn't work in the Script Pane when typing out $psISE.CurrentFile.Editor.... Sometimes it will work for the first '.', but not subsequent ones, sometimes it doesn't work at all, and sometimes the wrong intellisense menu is shown, such as showing the intellisense menu for $psISE.CurrentFile.Editor when I've only typed "$psISE." or "$psISE.CurrentFile.". The "workaround" to fix the intellisense is typically to just close and reopen PowerShell ISE.
Posted by SpikeX2 on 6/6/2013 at 11:55 AM
+1. I have also noticed that in some cases, intellisense will completely fail to show up for an identifier, consider the following code:

$wc = New-Object System.Net.WebClient

Sometimes, after this is declared in a function, typing "$wc." does not show a list of members while editing the function in the editor window. Even hitting Ctrl+Space does not open Intellisense.
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
ScreenCapture_11-29-2012 9.24.34 AM.wmv 11/29/2012 2.39 MB