Dying? Not really. In fact, it is quite perplexing to understand whether VB.Net is useful for future developments, but you cannot say it is dead in the market. Being one of the oldest languages, so many projects are still working on VB.Net in the companies. Though there may be a lot of new technologies emerging in the market, thinking to convert these projects into updated trends is not an easy task. It requires a lot of effort, time, and money for that. Therefore, it is quite clear to say - VB.Net is not going to vanish in the market in the upcoming future.
Any less demanding language in the market will stay at least for a substantial time frame. For instance, just consider VB6 which was declared as an Unsupportive language since a long ago but today still many firms working on the vast enterprise applications done through VB6. They are in a phase of migrating VB6 to VB.Net for future implementation.
More importantly, VB.Net uses the same libraries as that of C# in the .Net framework for web development. Therefore, many developers find it easy in using VB.Net, in fact, both have quite similar execution processes also. VB.Net code is easier to understand when compared to C#.
Another essential factor about VB.Net is that though people don’t find comfort in using this language anymore, it is still one of the favorite ones used for making GUIs in the Applications.
It is a fact that coding languages never die. Even the oldest coding languages such as Classic Asp, VB6, COBOL, FORTRAN, VB.Net, etc. are still in use in few organizations. As these have long coding standards that are already in huge numbers in the old projects, these languages have to be maintained in the market at least for understanding the code flow while conversion of Project.
VB.Net is not less when compared to PHP, Swift, etc., the reason for its downfall is people don’t like it to work with. And that’s why people started to focus on C# sidelining this language.
Though the world went to the other way, however, I must say there is nothing in C# which you can’t do in VB.Net.