[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu]
Patrick recently posted about something he found odd when installing the VS 2010 RC – which was that code intellisense for C# wasn’t working. When he pulled up Tools->Options and checked under the Text Editor->C# settings he noticed that the reason Intellisense wasn’t working was because his profile had them turned off – and he couldn’t understand why it was configured to be off by default:
Why does this happen?
The above situation occurs because:
1) When you run VS 2010 the first time on a machine that has had VS 2008 installed on it, it asks you if you want to import your existing VS 2008 profile settings. By default this checkbox is checked – which means you by default automatically import your existing settings.
2) Some VS plugins – for example Resharper – turn off the built-in C# code intellisense within VS and instead replace it with their own implementation. If you’ve installed Resharper on VS 2008, the above VS code intellisense profile settings are turned off. When you import your existing profile during VS 2010’s first time run experience the code intellisense settings import over in a disabled state. If you haven’t installed Resharper on VS 2010 (which is a separate install) – then by default you’ll end up with intellisense turned off.
How to Fix this?
Fixing this situation with the VS 2010 RC is pretty easy. Just do one of two things:
1) Use the Tools->Options menu command, select the Text Editor->C# settings, and then check the two circled check boxes above (Auto-list members and Parameter information). Intellisense will then be turned on and work fine.
2) Install the version of Resharper that works with the VS 2010 RC. It then enables intellisense using its own mechanism.
We are modifying the profile import behavior in the final release of VS 2010
We’ve heard reports of a few people running into this – and since the behavior is pretty confusing we are modifying the profile import behavior with the final release of VS 2010 to avoid it. If a plugin has turned intellisense off with VS 2008, by default when you import the profile into VS 2010 we will re-enable it. This will ensure that on a clean VS 2010 install intellisense always works by default.
Hope this helps,