Skip to main content

Keene Systems, Inc.

ASP.NET Application Support and Takeover

If your business depends on an ASP.NET application and the people who built it are no longer available, Keene Systems can take it over. We learn how the system works, write it down, fix what is broken and stay available for whatever it needs next. We have worked with ASP.NET since 2002, so no version of it is new to us.

The application works. The problem is who looks after it

Most business applications outlive the arrangement that produced them. The employee who wrote the system moves on. The small firm that built it closes or loses interest. The contractor takes a full-time job. The application keeps running, because good software does, but the list of things nobody can change gets longer every month.

Then something forces the issue: a server that has to be replaced, a security questionnaire from a customer, a new tax rule, a report the owner needs by Friday. That is usually when we get the call.

Experienced developer pointing at a computer screen while explaining a system to a colleague

Signs you need a new ASP.NET support team

  • The developer who built the application has left, retired or become hard to reach.
  • Small changes take weeks, or are quietly never done.
  • Nobody is sure where the source code is, or whether it matches what is running.
  • The application runs on a server or a version of .NET that is years out of date.
  • Staff keep spreadsheets on the side because the system cannot be changed.
  • A customer, insurer or auditor has asked security questions you could not answer.

How we take over an ASP.NET application

Taking over a system is a job in its own right, and we treat it as one. Our ASP.NET development team starts by getting the application running on our own machines from your source code and a copy of the database. If it will not build, that tells us something important straight away.

Then we read it. We look at how the code is organized, how it talks to the database, how users log in, what it connects to and how it is deployed. We note what is sound and what is fragile, and we check the things that are easy to overlook: whether backups are really running, who still has passwords, and which parts depend on software that is no longer supported.

You get a plain written account of the system’s condition. From there you have a team that knows it. The first piece of work is usually the list of fixes people have been waiting on.

What ASP.NET support covers

  • Fixes. Errors, pages that time out, reports that have stopped working, imports that fail.
  • Changes. New fields, screens, reports and workflows as the business changes.
  • Performance. Slow pages and slow queries, most often cured in SQL Server.
  • Security updates. Framework patches, expired certificates, old login methods and accounts that should have been closed.
  • Server moves. Getting the application off an ageing server and onto a current one, or into the cloud.
  • Integrations. Connecting the application to accounting, shipping, payment or reporting systems.
  • Upgrades. Moving from Web Forms or an old .NET Framework version to current .NET when the time is right.

Support from us is ongoing development by the same people each time, used when you need it. There are no minimums or monthly commitments.

Every version of ASP.NET, including the old ones

We have built on ASP.NET since its first release, so we still read the older styles fluently: Web Forms with code-behind in C# or VB.NET, the first MVC versions, Web API services, and the Classic ASP pages that many older systems still carry alongside. You do not have to modernize before we will help. Often the right first step is to make the existing system stable, and decide about modernization afterwards with facts in hand.

If the source code itself has gone missing along with the developer, that is a different problem with its own answer: see how lost .NET source code is recovered with a decompiler.

How we take over an ASP.NET system

  1. We talk it through. You tell us what the application does, who built it and what has gone wrong.
  2. We secure it. We confirm that backups work, that you hold the source code, and that only the right people have access.
  3. We learn and document it. Developers work through the code and the database and record how the system fits together.
  4. We clear the backlog. The fixes and small changes people have been waiting for come first.
  5. We stay. The same developers are there for the next request, with no minimums or monthly commitments.

The next step is a short, no-pressure conversation. Schedule an ASP.NET project exploration call or use the form on this page.

Frequently asked questions

Can you support an ASP.NET application you did not build?

Yes. Taking over applications built by someone else is a large part of our work. We review and document the system first, then take responsibility for fixes and changes.

What if there is no documentation?

That is normal. Very few business applications are documented. Producing a working description of the system is part of how we take it over.

Do you support ASP.NET Web Forms and VB.NET?

Yes. We have worked with ASP.NET since 2002 and still maintain Web Forms applications written in C# and VB.NET, as well as MVC, Web API, Blazor and ASP.NET Core systems.

Do we have to modernize the application first?

No. We can stabilize and support the application as it is. If modernization makes sense we will explain why and what it involves, and the decision is yours.

Do you require a monthly support agreement?

No. Support is ongoing development by the same team, used when you need it, with no minimums or monthly commitments.

How quickly can you start?

The first step is a conversation and a look at the code and database. In an emergency, such as a system that is down, tell us at the start and we will say plainly what we can do and how soon.

Schedule a Project Exploration Call

This free session is your fastest path to improved business productivity.