>Yes, I would agree with that. I have seen justifications for using C#, or its predecessor C++ or look-a-like, for being able to get closer to machine code and such.

Here I think you are wrong to group C# *compiled* code near to C++ (or Java, if you aim for syntax, brace style, garbage collection and intermediate code) - it still is closest to VB compiled IL code (at least when I checked, but that was before Roslyn...)

>The baseline, for me at least, remains that I can compile this under the .NET layer, which does it very well.

As you picked VB early on, I'd suggest a "Don't worry, be happy" mood as long as you also can decompile IL from VB code into corresponding C# code.
You might have to fix a few lines, but nothing in comparison to a total rewrite in another language. And if you decide to switch over, you can do it module by module or in a huge step mode - as you wish.

I can point fingers at MS for quite a few blunders, but not in that area ;-)