Legacy Code Survival Guide: Visual Basic and .NET in 2025

What's Still Alive, What's on Life Support, and What's Six Feet Under

Old, outdated code - the gift that keeps on giving... headaches. If you're managing applications built with Visual Basic or various .NET flavors, you're probably wondering: "Is this still supported, or am I one Windows update away from disaster?" Believe it or not, the GAP crew loves this topic so let’s help you understand the current state of these technologies as of mid-2025.

🧓 Visual Basic: The Veteran Still Standing

Visual Basic 6.0 (VB6)

• Status: The VB6 runtime is still supported on Windows, but only for existing applications. Microsoft’s stance is clear: "It Just Works" compatibility is the goal, but don't expect any new features or enhancements. learn.microsoft.com
• Support Details: The VB6 runtime support aligns with the support lifecycle of the Windows versions it runs on. learn.microsoft.com+1dotnet.microsoft.com+1
• Translation: If you're still running VB6 apps, they might continue to function, but you're on borrowed time. Start planning your migration strategy.

VB.NET

• Status: VB.NET is still supported and included in the latest versions of Visual Studio. However, Microsoft has shifted its focus to maintaining stability rather than introducing new features. learn.microsoft.com
• Support Details: VB.NET is part of the .NET ecosystem and benefits from the same support lifecycle as the .NET versions it targets. 
• Translation: Your VB.NET applications are safe for now, but don't expect any groundbreaking updates. It's a good time to consider transitioning to C# or another modern language for future development.

🧱 .NET Framework: The Old Guard

• .NET Framework 4.5.2, 4.6, 4.6.1: Support ended on April 26, 2022. These versions are no longer receiving security updates or technical support. stackoverflow.com+4dotnet.microsoft.com+4learn.microsoft.com+4
• .NET Framework 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8: Still supported as they are considered components of the Windows operating system. Their support lifecycle aligns with the Windows versions they are part of. 
• Translation: If your applications target .NET Framework 4.6.2 or later, you're still in the clear. However, for new development, Microsoft recommends using .NET (formerly .NET Core).  dotnet.microsoft.com+2learn.microsoft.com+2learn.microsoft.com+2

🚀 .NET (Core and Beyond): The Modern Era

.NET Core 3.1

• Status: Reached end of support on December 13, 2022. learn.microsoft.com+5devblogs.microsoft.com+5dotnet.microsoft.com+5
• Translation: Time to upgrade. .NET Core 3.1 is no longer receiving updates or support.learn.microsoft.com+1devblogs.microsoft.com+1

.NET 5

• Status: Reached end of support on May 10, 2022. devblogs.microsoft.com
• Translation: If you're still on .NET 5, you're in unsupported territory. Upgrade to a supported LTS version.

.NET 6 (LTS)

• Status: Support ended on November 12, 2024. devblogs.microsoft.com+1endoflife.date+1
• Translation: .NET 6 is no longer supported. It's advisable to move to .NET 8 or later.

.NET 7

• Status: Reached end of support on May 14, 2024. infoq.com+1devblogs.microsoft.com+1
• Translation: .NET 7 is out of support. Upgrade to a supported version to ensure continued security and technical support.reddit.com+6stackoverflow.com+6infoq.com+6

.NET 8 (LTS)

• Status: Released in November 2023, with support until November 2026. 
• Translation: .NET 8 is the current Long-Term Support (LTS) version. It's the recommended target for new development and for upgrading existing applications.

📊 Quick Reference Table

🧭 Final Thoughts

Managing legacy code is like maintaining a classic car - it requires care, attention, and sometimes, a complete overhaul. Here's what you should consider:

• For VB6 Applications: Start planning your migration strategy. While your applications might still run, they're on borrowed time.
• For VB.NET Applications: They're still supported, but in maintenance mode. Consider transitioning to C# or another modern language for future development.
• For .NET Framework Applications: If you're on version 4.6.2 or later, you're still supported. However, for new development, target .NET 8 or later.
• For .NET Core and .NET 5/6/7 Applications: These versions are no longer supported. Upgrade to .NET 8 to ensure continued support and access to the latest features.

Remember, staying updated isn't just about access to new features—it's about security, performance, and peace of mind.

Need assistance with migration strategies or have questions about specific scenarios? Contact Us!