How Microsoft Built A Feature I Will Never Use

I just got a response on my suggestion on ladybug regarding keyword autocompletion on Visual Studio 2005:

At this point in time, intellisense allows you to get a list of available keywords and code snippets as you type. This is a very nice functionality (even though I have disabled it for the time being), but it can be improved, as these ‘suggestions’ are likely to break your code, syntax-wise. Take, for instance, the case where you write a public instance method that returns an instance of a type which starts with the letters “pub”. Hitting Ctrl+Space after writing ‘pub’ for the first time completes to ‘public’, but the second one would do so as well, even though the keyword ‘public’ is illegal in that context. This is one of the only things that keeps me from enabling this option.

I’m pretty sure that I’m not the only one that’s annoyed by this problem.

Jay replied:

… I hope that in the next version we’ll get a lot smarter about keywords we show, which I will be a nice thing for all users, and a huge win for novice C# users.

Which, in effect, means that we will not be seeing this upgrade until Visual Studio Orcas.

This is a total waste of feature:
Imagine intellisense in the XML editor in Visual Studio. When faced with a known schema for the current file, it will let you choose the appropriate element for the context it is inserted into (if A can only be nested under B, it will only show A in the completion list when inside a B element).
Imagine the XML editor devoid of that ability – showing you every single declared element in the schema. Would you use that?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s