VB.NET Support & C# Migration Australia

Overview

VB.NET has been Microsoft's managed, object-oriented Visual Basic since 2002, and it still underpins a large share of enterprise line-of-business applications, WinForms desktop tools and ASP.NET back ends. Most of these codebases carry the habits of several different .NET eras layered on top of each other.

What we handle

Ongoing maintenance and feature work directly in VB.NET
Untangling business logic from UI code so it can be tested and reused
Incremental, interoperable migration to C# only where it adds real value
Upgrading target framework versions and dependencies safely
Documenting the parts of the system that live in one person's head

What this usually looks like

Signs your VB.NET system needs a specialist, not a generalist.

Codebase mixes conventions from several different .NET eras
No tests around the business-critical logic that actually matters
The original architecture decisions were never documented
The team wants to move to C# but can't justify a full rewrite
A WinForms UI tightly coupled to business logic underneath it

The bridge

Old and new, working together

Extract core business logic out of a WinForms VB.NET application into a shared library that both the legacy desktop app and a new web front end can call.

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 VB.NET right now?

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

Get in touch