I suggest you ...

improve c# intellisense

Intellisense does not seem to act any differently when you are typing an argument for a method.

Eclipse's intellisense was able to suggest items based on their type and the current argument that your cursor was in when calling a method.

Visual Studio will suggest items based on previous usage or currently typed characters, regardless of whether it makes sense.

For example, I have a enum type called "LogType" and a delegate called "LogTextDelegate." I also have a method with the prototype
void Log(string text, LogType type)

If I type the following, Visual Studio keeps suggesting "LogTextDelegate" instead of the obvious/helpful choice of "LogType":

Log("Message to log", Log

Perhaps VS intellisense could be improved?

(this is from a MS Connect suggestion: http://connect.microsoft.com/VisualStudio/feedback/details/665497/intellisense-could-be-improved-when-suggesting-values-for-a-method-argument)

12 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CalebCaleb shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • DirkDirk commented  ·   ·  Flag as inappropriate

        I would give this one a million votes if I could. Additionally if a method is selected VS could add the brackets and add a semicolon (C#) and place the cursor inbetween them.

      Feedback and Knowledge Base