>>>>> Of course the argument most often put forward by the VB camp for WITH....ENDWITH is that it reduces the amount of typing required.
>>>>
>>>>Some time ago I finally switched from VB.NET to C#. As silly as it sounds, one of my reasons was the necessity to use underscores in VB multi-line statements.
>>>>
>>>>I agree that ending statements with the semicolon is also questionable. But for me the underscores were much worse.
>>>
>>>As Craig pointed out you can (mostly) rely on implicit line continuation in VS2010. But I just do not like the general verbosity of VB. eg

static string X(out string s, int[] i) { }
>>>becomes:
>>>Private Shared Function X(ByRef s As String, i As Integer()) As String
>>>End Function

So VB requires twice as many characters :-}
>>
>>Someones gotta say it , VB sucks !!! Lol
>
>Don't get me wrong. VB is fine. And whether VB or C# - when it's compiled it's pretty much identical. Use the one your comfortable with - it's just that, for me, that one is C#....

I know what you mean, I think I fall into the 'old gits' category, when I see a routine written in both C# and VB side by side, the C# version just looks much more professional and ( dare I say it ? ) elegant - but that's 'old gits' for you :-)