# Microsoft Plots the End of Visual Basic **URL:** \ **Category:** News & Articles\ **Tags:** technology, windows\ **Created:** [March 14, 2020, 1:51pm UTC](https://onehack.st/t/microsoft-plots-the-end-of-visual-basic/73367 "2020-03-14T13:51:25Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Shayla](https://onehack.st/user_avatar/onehack.st/shayla/32/174870_2.png) [@Shayla](https://onehack.st/u/Shayla)\ **Post date:** [March 14, 2020, 1:51pm UTC](https://onehack.st/t/microsoft-plots-the-end-of-visual-basic/73367/1 "2020-03-14T13:51:26Z")
![image](https://onehack.st/uploads/default/original/3X/1/f/1f65853273550c7e2e5ed7cc4de2fb66bbeb10e8.jpeg) Microsoft said this week that it will support Visual Basic on .NET 5.0 but [will no longer add new features or evolve the language](https://www.thurrott.com/dev/232268/microsoft-plots-the-end-of-visual-basic). From a report: _“Starting with .NET 5, Visual Basic will support Class Library, Console, Windows Forms, WPF, Worker Service, [and] [ASP.NET](http://ASP.NET) Core Web API … to provide a good path forward for the existing VB customer who want [sic] to migrate their applications to .NET Core,” the .NET team wrote in a post to the Microsoft DevBlogs. “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 Core and .NET Framework versions of Visual Basic.”_ _When Microsoft released the .NET version of Visual Basic, originally called Visual Basic .NET, alongside C# at the beginning of the .NET era, the two languages were evolved together and had roughly identical feature sets. 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 versions of the environment. Today, virtually all of Microsoft’s relevant developer documentation is in C# only, with VB source code examples ever harder to find._