Back in 2008 I posted a suggestion on Microsoft’s Connect website. To be precise the date was 15th May 2008. To my surprise I received an email today (5th August 2010) informing me that there is a comment on my suggestion. It only took a little more than 2 years. Wow! talk about a speedy response. “What’s wrong with Microsoft” will be a topic for another post. Today I want to revisit my suggestion. It’s about Intellisense. Here it is exactly how I posted it on Connect site.

Problem Statement

At present we have Ctrl + . which opens intellisense and lists all methods, properties events available for the corresponding object. There are times when I and I assume other users are only interested in looking at either events, methods or properties.

Proposed Solution

I suggest the following shortcuts which will filter the list:
Ctrl + . + p – Display only properties
Ctrl + . + e – Display only events
Ctrl + . + m – Display only methods

And the response from Microsoft today is:

Thanks for taking the time to submit this suggestion! I sincerely apologize for the amount of time that has taken to get back to you.
When we locked down on our final feature set for the next version of Visual Studio, IntelliSense completion set filtering for member types didn’t make the cut–though it was considered. However, his is a commonly requested feature, and we’ll consider it for a future release of Visual Studio. Please feel free to contact me directly at … if you have any further thoughts.

I am glad to know that this will at-least be considered for a future release. I’ll be happy if it ever gets implemented.

Tagged with:
 

3 Responses to Intellisense Enhancements I want

  1. Dave says:

    Talking about a wrong statement. So, this is a common requested feature (read: a lot of developers want it), but it didn’t make the cut.

    So I started searching connect for help documentation issues related to VS2008 and earlier. And guess what? Only one issue that the document explorer can’t be pinned to the desktop in Windows 7.

    So they destroyed a good working help system (what nobody requested) and stuff that we (developers) want isn’t implemented.

    I think the Microsoft Visual Studio team has the wrong priorities..

  2. Deepak says:

    Overall I have to give it to MS. IMO Visual Studio is a good product. However people management or let’s say customer management side of MS is not working properly. There is too much noise and messages get lost.

  3. Dave says:

    Well, because of the terrrible new help system in VS2010 (no index, no treeview toc) we’re still working with VS2008. WPF designer/code views are a lot slower than in VS2008. Help system cannot be installed on IIS or shared with other users, so we have to download the help packages more than 100 times! In reality that means that VS2010 decreases productivity with about 10-12% around here in comparison with VS2008.

    MSDN online has three different layouts. Why haven’t they copied those? We are professional developer, we know we what to know, we know were it’s located, but currently you get RSI if you want to see the arguments of an method.

    Due to the new WPF based editor enhancement tools like ReSharper cannot color highlight all the different syntax elements like in VS2008. More on a personal note, I am still amazed that VS doesn’t come with an (optional) dark theme. I have three 24″ screens here and they admit a lot of light. Before I started changing the colors in VS I had from time to time headaches. At night, I can light the room with the standard (white) VS theme.

    However, TFS2010 is a gem. It’s the best version control system I have ever seen and I have seen a lot (cvs, svn, git, arch, vss, etc). I also think VS2010 has a lot of potential, but it needs a lot of finishing touches.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>