Ok, so C# transformation of an existing VB.NET project isn’t quite as “smooth” as I would like, but it brings benefits of drilling in the whole “;” syntax.
Also what comes to a screaming head is the fact that in VB.NET you can get away with a lot under “normal” circumstances. You know, the one where you don’t declare “Option Strict On”. So porting to C#, the compiler conditionally complains of things like:
Cannot implicitly convert type 'int' to 'string'
Currently, I’m telling it what to do:
foo.ToString();
Specifically telling computers what to do is an inherently good thing for programmers. Especially if you’re a control freak like me. Another “good thing” - touch-typing.