When they go out of their way to say VB is a first class component and repeatadly say over many years that c# is not a replacement for VB then yes, I do think i

When they go out of their way to say VB is a first class component and repeatadly say over many years that c# is not a replacement for VB then yes, I do think it's realistic to expect them to support it. That said, despite what MS has said the writing has been on the wall for VB.net since day one and it was only ever a transitional path for VB classic. The companies that never made the transition are the ones you generally want to avoid, the types of companies still using VB are generally using a lot of other dead end tech like web forms or TFS. Some design decisions in VB stood the test of time remarkably well, dim/var to declare a variable and type declaration on the right now seem to be features of most new languages.