Intellisense autocompletion triggers differently in VS2012 than in VS2010. Can it be configured?

Question

In VS2010 when you start writing something in the editor which triggers the intellisense, it would automatically select an item from the list for you, so that you only had to press one of the trigger buttons to autocomplete. For instance if you wrote "Sys" followed by the period sign, it would autocomplete to "System.". This is not so in Visual Studio 2012 Express RTM. Here you must manually select an item first with Arrow Down before clicking a trigger button. Illustration below.

This extra key press requirement is annoying, as I have gotten used to the autocompletion routine from VS2010. Is there any configuration setting which enables the VS2010-style of autocompletion in VS2012?

Note: I do have "." (period sign) in my commit character list configured in Options > Text Editor > C# > Intellisense. I also have checked "Pre-select most recently used member" in both VS2010 and 2012.

Answer 1

It is working correctly for me in Ultimate.  As far as I know Intellisense behaves the same between both editions.  Do you have any extensions installed?

Michael Taylor - 9/28/2012
http://msmvps.com/blogs/p3net

Answer 2

Nope, clean installation. Are you sure the behaviour is the same between the editions? Would be interesting to hear from someone else who have tested Express edition

Answer 3

It works the same in the various editions of Express as well.  I verified on my clean installs.  Try exporting your settings, resetting to defaults and trying again.

Michael Taylor - 9/29/2012
http://msmvps.comm/blogs/p3net

Answer 4

That did it! I'm still curious to know which particular setting does this though... But my problem is solved :)

Answer 5

I also meet this problem. I restore to default option, but the problem remain unsolved.  Please help!

Answer 6

After restoring to defaults did you run in safe mode?

Michael Taylor - 11/24/2012
http://msmvps.com/blogs/p3net

Answer 7

After restoring to defaults did you run in safe mode?

Nope.

Actually, I've experienced it a lot lately, but now it's fixed for me by simply restarting Visual Studio.