Will .NET team terminate VB support in near future?

Well, not an easy question to respond to. My guesses are that if you want to continue programming in VB, it does mean VB.Net. In this case, since many of the .NET framework are only in C#, I suggest that you understand a little bit of C#. That's what I am currently doing. I develop my mockups in VB.Net, stay with it if reasonably efficient, then go for a C# version of it, that I try to keep in parallel, but with less testing. A C# to VB.Net translator is available for free, developed by the C# team. The same that developed the VB.Net compiler I suppose. That should give you a reasonable starting response point.

I think that the decision on put VB in "dead mode" is a grave error (as many other) take from Microsoft. It is the real first visual language and now should stay in 1 position at place of Python. When you forget and not respect your history you pay a price...