Classic ASP & VBScript Support Australia

Overview

Classic ASP and VBScript power a large number of intranets, extranets and internal business tools built between the late 1990s and mid-2000s. It's page-based, mixes logic directly into markup, and leans on COM objects for anything beyond basic requests. The applications built on it are frequently still running the core of a business, long after the team that wrote them has moved on.

What we handle

Bug fixes and feature additions inside existing ASP files, without a rewrite
Tracing and resolving Server object, ADO and ODBC connection errors
Auditing and hardening session handling and inline SQL against injection risk
Exposing existing ASP functionality through a modern API layer
Planning a realistic, staged migration path when the business is ready

What this usually looks like

Signs your Classic ASP & VBScript system needs a specialist, not a generalist.

Pages built as .asp files with inline SQL and VBScript
No separation between logic and markup, making changes risky
Dependence on COM objects registered years ago, with no record of how
The developers who built it left the industry, not just the company
IIS and application pool configuration nobody has touched in a decade

The bridge

Old and new, working together

Wrap a Classic ASP page's business logic behind a modern C#/.NET API, so newer systems can integrate with it without anyone touching the original VBScript.

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 Classic ASP & VBScript right now?

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

Get in touch