Visual Basic is the odd man out in the new .NET

C# is the future for .NET developers, so it's time to limit Visual Basic’s use to on-premises legacy systems

In a series of blog posts last week, Microsoft detailed fundamental changes to how it develops its .NET languages. It was good news for C# and F# developers, but while Microsoft put a positive spin on what the changes meant for Visual Basic, the long-term future of the venerable language seems less certain.

Microsoft’s Visual Basic has long been one of the world’s if not favorite, then certainly one of the most widely used languages, and it really put Microsoft at the center of the enterprise stage. From its first six iterations as a language for client-server application development to its rebirth as part of the .NET platform, Visual Basic has been the go-to tool for quick development of enterprise applications. That’s in part because of its massive library of user interface components, along with connectors to common databases and a component model that’s allowed third parties to build businesses on providing additional functionality.