Legacy Application Support & Modernization
Many businesses depend on applications built years ago in Classic ASP, PHP or earlier versions of .NET. They still do important work, but it gets harder to find someone who can maintain them. I've worked with these technologies for many years, and I still work with them today.
Applications I work on
- Classic ASP applications with SQL Server, MySQL or MS Access databases
- Existing PHP applications, including custom code written by other developers
- Older ASP.NET and .NET applications
- JavaScript and jQuery front ends that need fixes or updates
Typical work
Bug fixing and troubleshooting
Finding and fixing errors, including the intermittent ones that are hard to reproduce, across the code, the database and the server configuration.
Maintenance and changes
New fields, new reports, changed business rules and small features: the everyday changes a working system needs.
Security improvements
Older code often predates current practice. I can review and fix common weaknesses such as unsafe database queries, missing input validation and outdated handling of passwords and forms.
Compatibility improvements
Keeping an application working when the environment changes: a move to new hosting, a newer PHP version, server or email changes, or browsers that no longer behave the way the code expects.
Taking over from another developer
If your original developer has moved on, I can learn the system, document how it works and take over its maintenance. For example, I took over the programming and maintenance of an existing Classic ASP site for Nannys and fixed many bugs so the site runs smoothly.
A complete rewrite isn't always necessary
When an application is old, it's tempting to start again from scratch. Sometimes that's right, but rewrites are expensive, take longer than expected and have to rediscover years of business rules hidden in the existing code. Meanwhile the old system still has to keep running.
Often a better route is to modernize gradually:
- stabilize the system and fix what causes the most trouble
- improve security and compatibility so it can keep running safely
- move logic into well-structured stored procedures or services
- build new parts, such as an ASP.NET Core API or a React screen, alongside the existing application
- replace older sections one at a time, when it's worth it
The business keeps working throughout, and each step delivers something useful. If I think a rewrite really is the better choice for your situation, I'll tell you that too.
Getting started
Usually I need access to the source code, the database and the hosting or server. I'll review the system, tell you what I find in plain language and suggest where to start.
Related services
- SQL Server and database development
- Ongoing developer support for systems that need regular attention
- Custom software and integrations for new parts of a modernized system