Microsoft has always been about the profit and VB.NET is not a cash cow although Microsoft has a commitment with VB.NET but not to keep C# in alignment with new features as they are with C#.
There are several groups on the web that look at enhancing VB.NET such as VB Dev2Dev which I'm a member on GitHub.
In some cases if a developer understands basics of C# and have found code that can not be translated to VB.NET because something is not supported they can create class projects, reference the C# class project in their VB.NET projects and use them while this does not always work.
In the end, Microsoft announced just last week pretty much what I wrote above and that I seem to be one to look at for code samples moving forward.
And lastly, combine what I mentioned coupled with @Duane Arnold and you have a clear picture for VB.NET future.