Quote Originally Posted by NickThissen View Post
Y
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:

I clearly entered a Rectangle, yet intellisense still thinks I entered a Point...
Must be either some setting you've got or just C#, cos I just tried that exact same scenario in VB 2010 Express and it worked as expected, selecting the correct overload once I had entered a Rectangle