What this means to VB developers is that they might be able to bring their existing codebases forward to. This week’s announcement just makes it official. But that never really happened, and Microsoft effectively abandoned VB.

Only C# would get all of the new features, while VB would focus on the simpler and more approachable scenarios that it once dominated.

Worse, Microsoft in 2017 announced that its original C#/VB co-development strategy was over. Today, virtually all of Microsoft’s relevant developer documentation is in C# only, with VB source code examples ever harder to find. But this changed over time, with professional developers adopting C# and many fans of classic VB simply giving up on the more complex but powerful. NET era, the two languages were evolved together and had roughly identical feature sets. NET, alongside C# at the beginning of the. NET version of Visual Basic, originally called Visual Basic. “Going forward, we do not plan to evolve Visual Basic as a language … The future of Visual Basic … will focus on stability, the application types listed above, and compatibility between the. NET team wrote in a post to the Microsoft DevBlogs.

NET 5, Visual Basic will support Class Library, Console, Windows Forms, WPF, Worker Service, ASP.NET Core Web API … to provide a good path forward for the existing VB customer who want to migrate their applications to. NET 5.0 but will no longer add new features or evolve the language. Microsoft said this week that it will support Visual Basic on.

Visual basic express