What Happened to Visual Basic?
Visual Basic, a programming language and integrated development environment (IDE) from Microsoft, revolutionized rapid application development for Windows in the 1990s. While its classic version (VB6) reached end-of-life for its IDE in 2008, its runtime remains supported for compatibility with existing applications. Its successor, Visual Basic .NET (VB.NET), introduced in 2002, is currently in maintenance mode as of 2020, meaning no new language features are being added, though it continues to be supported for bug fixes and compatibility within the .NET ecosystem, including Visual Studio 2026.
Quick Answer
Visual Basic exists in two main forms: Classic Visual Basic (VB6 and older) and Visual Basic .NET (VB.NET). Classic VB's IDE stopped being supported in 2008, but its runtime is still maintained for compatibility with legacy applications on modern Windows. VB.NET, while still supported in Visual Studio 2026 and .NET 8/9 for bug fixes and existing projects, entered a maintenance-only phase in 2020, with Microsoft no longer adding new language features. Many mission-critical applications still run on VB6, but organizations are increasingly urged to migrate due to security risks and lack of modern development capabilities.
📊Key Facts
📅Complete Timeline15 events
Visual Basic 1.0 for Windows Released
Microsoft introduces Visual Basic 1.0 at the Comdex/Windows World trade show, marking a significant step in rapid application development for Windows with its visual interface and event-driven model.
Visual Basic 1.0 for DOS Released
A DOS version of Visual Basic is released, though it was less compatible with its Windows counterpart and used extended ASCII characters to simulate a GUI.
Visual Basic 6.0 (VB6) Released
The final version of 'Classic Visual Basic', VB6, is released. It becomes immensely popular for developing business applications on Windows, with an estimated two-thirds of all such programming done in VB.
Visual Basic .NET (VB 7.0) Debuts
Microsoft introduces Visual Basic .NET as part of the .NET Framework, a complete redesign that is incompatible with previous Visual Basic versions, aiming for a modern object-oriented language.
Mainstream Support for Visual Basic 6.0 Ends
Microsoft officially ends mainstream support for Visual Basic 6.0, signaling its transition to a legacy product.
Visual Basic 6.0 IDE Support Ends
Microsoft officially stops supporting the Visual Basic 6.0 Integrated Development Environment (IDE), though it commits to maintaining runtime compatibility for existing VB6 applications on Windows.
VB.NET Enters Maintenance Mode
Microsoft announces that Visual Basic .NET will no longer receive new language features, effectively placing it in a maintenance-only mode, with focus shifting to C# for new .NET innovations.
Microsoft Reaffirms VB.NET Strategy
Microsoft updates its programming languages strategy, confirming its commitment to maintaining VB.NET's stability, C# interop, and Visual Studio features for core scenarios, but reiterates no plans for new language features or workloads.
VBScript Deprecation Announced
Microsoft announces its plan to gradually deprecate Visual Basic Script (VBScript) in favor of more modern scripting languages like JavaScript and PowerShell.
VBScript Becomes On-Demand Feature
As part of its deprecation plan, VBScript becomes available as an on-demand feature in Windows 11 version 24H2, no longer installed by default.
VB.NET Status in 2025
Analysis confirms VB.NET is still supported and included in Visual Studio, but in maintenance mode with no new features, urging developers to consider C# for future development.
VB6 Still in Use, Posing Risks
Despite being obsolete, Visual Basic 6.0 is still used by thousands of businesses for mission-critical applications in 2026, creating significant security, compatibility, and maintenance risks.
VB.NET Confirmed in Maintenance Mode for 2026
A freelance developer's report confirms VB.NET is in maintenance mode in 2026, with no new language features, a shrinking community, but still compiling and running on .NET 8 and .NET 9.
VB.NET Issues Reported in Visual Studio 2026 Update
Users report issues with VB.NET in a recent Visual Studio 2026 update, showing numerous errors during development, although projects still compile.
VBScript FODs No Longer Enabled by Default
In the second phase of VBScript deprecation, its Features On Demand (FODs) will no longer be enabled by default in Windows, requiring manual activation for continued use.
🔍Deep Dive Analysis
Visual Basic emerged in 1991 as a groundbreaking tool for Rapid Application Development (RAD) on the Windows platform, quickly gaining immense popularity for its visual approach to GUI design and event-driven programming. The final iteration of 'Classic Visual Basic' was VB6, released in 1998, which became dominant in business application programming. However, a significant turning point arrived in 2002 with the introduction of Visual Basic .NET (VB.NET) as part of the new .NET Framework. This was a complete rewrite, incompatible with VB6, aiming to modernize the language with object-oriented features and integrate it into Microsoft's broader .NET ecosystem alongside C#.
The divergence created a split in the developer community. Microsoft officially ended mainstream support for VB6 in 2005 and its IDE support in April 2008, effectively relegating it to legacy status. Despite this, Microsoft committed to ensuring the VB6 runtime environment would remain compatible with supported Windows operating systems due to the vast number of critical business applications built with it. This 'It Just Works' compatibility has meant that, as of 2026, thousands of businesses still rely on legacy VB6 applications for mission-critical tasks, particularly in sectors like healthcare, finance, and retail.
For VB.NET, the journey saw it initially as a co-equal to C# within the .NET framework. However, over two decades, the developer community and Microsoft's innovation largely consolidated around C#. In 2020, Microsoft made a pivotal announcement: VB.NET would no longer receive new language features, effectively entering a maintenance-only mode. This strategy was reaffirmed in February 2023, with Microsoft stating a commitment to maintaining VB.NET's stability, C# interoperability, and Visual Studio features for core scenarios like Windows Forms and libraries, but no plans to extend it to new workloads.
As of May 2026, VB.NET continues to compile and run on the latest .NET versions, including .NET 8 and .NET 9, and is supported in Visual Studio 2026 for bug fixes and compatibility. However, new frameworks and APIs like Blazor and .NET MAUI are C#-only, further limiting VB.NET's relevance for new development. The continued reliance on legacy VB6 and VB.NET applications presents growing risks, including security vulnerabilities due to lack of updates, compatibility challenges with modern architectures, and scarcity of developers with specialized knowledge. Organizations are strongly advised to plan migration strategies to modern alternatives like C# within the .NET ecosystem or low-code platforms to mitigate these risks and ensure future scalability and security.
Separately, Visual Basic Script (VBScript), a distinct scripting language introduced in 1996, is also being phased out. Microsoft announced its deprecation in October 2023, with VBScript becoming an on-demand feature in Windows 11 24H2 in the second half of 2024, and expected to be fully retired from future Windows OS releases.
What If...?
Explore alternate histories. What if Visual Basic made different choices?