>>>>> 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
>
>
>The problem I have experienced with VB is that it will let you do things that may work and then break when you release an application to production. C# does not let you get away with anything.

That's less true than it was before C# 4.0. Some of the new features allow you to compile cleanly, then blow up at run time.