ASP.NET MVC Maintenance & Migration Australia

Overview

ASP.NET MVC succeeded Web Forms from 2009 onward, separating models, views and controllers, and it still runs a large number of mid-2010s enterprise web applications built before the move to ASP.NET Core.

What we handle

Maintenance, bug fixes and new features within the existing application
Refactoring controller and business logic into a more maintainable shape
Planning and executing a staged move to ASP.NET Core where it's warranted
Keeping the application secure and supportable in the meantime

What this usually looks like

Signs your ASP.NET MVC system needs a specialist, not a generalist.

Built on an older MVC or .NET Framework version that's fallen behind
Controller logic grown large and tangled over years of additions
Razor views mixing display logic with business logic
No clear path from MVC on .NET Framework to ASP.NET Core

The bridge

Old and new, working together

Move the application's API layer to ASP.NET Core first, while the existing MVC front end keeps serving users, then migrate the UI once the foundation is solid.

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

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

Get in touch