Anyway, I'm sorry, this is completely off topic, but there is one thing that's bugging me a little about VS2010. I like it a lot more than beta 2, that's for sure, but this is bugging me.
In a C# project (probably VB too but too lazy to test right now) in VS2008, the autocomplete / intellisense list seemed a little 'smarter' than in VS2010.
Example: In a form, I type
In VS2008, the first available (matching) option ("AcceptButton") is selected, and I can press Enter to accept it.
In VS2010, the option is only 'highlighted' (with a border around it), but not really selected, and I have to complete the entire word, or press the up or down arrow, to select it and only then can I use Enter to complete it. Makes it pretty useless, no?
I'm not actually sure if this is default VS2008 behavior, since I have ReSharper installed, but I told ReSharper in the options to use the Visual Studio Intellisense, and not its own, so it should work as by default...
Also, I am still missing a feature that VB has had in VS2008 already (possibly also before that, don't know). If you are entering arguments in a method call that has a number of overloads, VB automatically picks the first one that matches the arguments you have already typed.
For example, the first constructor of the LinearGradientBrush takes two Points, and then two Colors. But there is also an overload with a Rectangle and two colors. If, in VB, I enter a Rectangle as the first argument,
Code:
Dim b = New LinearGradientBrush(New Rectangle(1,2,3,4),
then the Intellisense popup changes to the other overload, which starts with a Rectangle, so I can see what it expects next.
In C# however, in both 2008 and 2010, it doesn't pick up the fact that I'm trying to use a different overload, and it still shows me the 'wrong' overload:
http://www.vbforums.com/images/ieimages/2010/04/1.jpg
I clearly entered a Rectangle, yet intellisense still thinks I entered a Point...
Does this have to do with C# not having a background compiler? I thought it did have one since SP1? I really hoped they would have 'fixed' this in 2010, since it's been around since at least VS2008 for VB...
Or am I completely missing something... Some setting perhaps?