Visual Basic 6 (VB6) Support & Maintenance Australia

Overview

Visual Basic 6 has been officially unsupported by Microsoft since 2008, and it is still running point-of-sale systems, manufacturing control software and internal line-of-business tools across the country. The applications work; the risk is that almost nobody left in the industry can safely change them.

What we handle

Getting the VB6 toolchain running again on modern Windows or in a VM
Tracing and fixing runtime and COM registration errors after OS upgrades
Adding features and fixing bugs directly in the existing VB6 codebase
Wrapping VB6 components so modern .NET applications can call them
Planning a component-by-component migration path, not a risky rewrite

What this usually looks like

Signs your Visual Basic 6 system needs a specialist, not a generalist.

The application still runs, but the original developer left years ago
The VB6 IDE won't install cleanly on current Windows
OCX and DLL registration errors on new or reimaged machines
Nobody wants to touch the codebase because the dependency chain is unclear
A routine OS or hardware upgrade unexpectedly breaks a working system

The bridge

Old and new, working together

Expose a working VB6 component through .NET Interop so the rest of the business can build on modern infrastructure without replacing the piece that still works.

Related technologies

Classic ASP & VBScript 1996 – 2010s Visual Basic 6 1998 – 2008 COM, COM+ & ActiveX 1993 – present ASP.NET Web Forms 2002 – 2013 VB.NET 2002 – present C# 2002 – present .NET Framework 2002 – 2019 ASP.NET MVC 2009 – 2019 SQL Server 1998 – present Internet Information Services (IIS) 1995 – present

Running Visual Basic 6 right now?

Tell us what's going on — most first conversations take fifteen minutes.

Get in touch