Ed,
Interesting points. I can see how you don't like a MS language being called beautiful.. that was a bit of a strech, I'll admit. However, any language I practically already know just by knowing a couple other languages (very very commonly known and used languages, java/c++) would have to be called intuitive by those folks. It's sort of like Yiddish. If you know german, your're 90% there. Maybe intiuitive isn't the right word afterall.
I like your description of VB as verbose. Never used that particular word to describe it, but it definitely fits. Hey, some people like hemingway, and those people would like VB! I can see it being a matter of taste there.
It's strange, however, that you say that terminating semicolons and statement blocks defined by curly braces are outdated, though. I can think of few modern OO languages (or non oo languages for that matter) that don't use some sort of statement terminator and statement block. I always thought that VB's assumption that all statements were on their own line (unless you supply a line continuation character '_') was pretty unusual (and irritating). Also, VB has something similar to the semicolon. Basically the compiler terminates a statement when either it hits a new line (without encountering a terminating underscore), or when it hits a colon (ala the C# semicolon). I'm sure you know this already, but some who read this may not. One could imagine the compiler replacing all CR/LF characters with colons except where one finds an underscore.
Statement terminators encourage one to spread out one line of code to multiple lines to improve readability. Having tell the compiler to add the next line to the previous line seems a bit strange, and discourages alterations to the code that are simply there to improve readability (like spacing out parameters to multiple lines so they fit on one screen. Granted it's only one character, but it's something.
Regarding statement blocks, VB has Begin and End. Begin and End tags do take a bit more work to type (if you're lazy), but they definitely make the code less visually symmetric(statement block characters don't line up perfectly because Begin and End have different lengths!). I rely heavily on the curly braces to define scope and flow, and can do this by very quickly skimming through code. I always put the curly brace on its own line personally, for this reason, but that's an entirely different subject and purely a matter of taste.
I wanted to try to stay away from specific gripes about VB, but I felt that warranted a response. This is just the tip of the iceberg for me too (I like griping :-). I'm sure the C# gripes will soon flow :-) There's plenty of room for improvemet in all things.
Anyway, this has been an interesting exchange so far! Thanks for responding with such ferver! It seems no one wants to support C# for use in DNN core, which is OK. As Stephen Colbert says, the market has spoken.