Oh come, on: "without even trying to make it easy for people to convert their old code." VB.NET and C# even run in the same VM. You can trivially call from on

Oh come, on: "without even trying to make it easy for people to convert their old code." VB.NET and C# even run in the same VM. You can trivially call from one language into code written in the other. The object system is (necessarily) a direct mapping, at least in the direction he's interested in, so even translating VB.net to C# shouldn't be a problem where keeping a particular piece of code in VB isn't practical for extending it.