What It Costs Per Year to Keep Running a .NET Framework Application

.NET Framework 4.8 costs nothing to keep. It ships with Windows and is supported for as long as the Windows version underneath it. The annual cost of holding position comes from everything around the framework, and it can be itemized.

The line items

The operating system. The application is supported only while its Windows Server version is. Once that version leaves support you are paying for Extended Security Updates, where available, or carrying a documented exception. Infrastructure has this figure.

The database. SQL Server versions age out on the same schedule. SQL Server 2014 left extended support in 2024 and SQL Server 2016 in July 2026.

Components with no supported version. Reporting engines, grid controls, PDF libraries and vendor SDKs pinned to an old release. Cost here shows up as security findings and as features that cannot change.

Scheduled breakage. Something external changes every year: a partner retires TLS 1.0 and 1.1, an API version is switched off, a certificate chain changes, a browser drops a behavior the UI relied on. Each one is a few days of unplanned work. Count the incidents from the last two years.

Security and compliance time. Hours spent answering questionnaires, writing exceptions and remediating scan findings that exist only because of the platform's age. The security lead or whoever handles client audits has these.

Maintenance hours. What you pay, internally or externally, to keep it running and make small changes. On an older stack each change takes longer because tooling, test coverage and documentation are thinner.

Staffing. Fewer developers want Framework and WebForms work each year. That shows up as longer searches and higher rates. HR or your last recruiting invoice has the number.

Deferred work. Features the business asked for and was told the platform could not support. Product or operations can list them.

Add the first seven for the last twelve months. That is the yearly cost of doing nothing, and it tends to rise each year.

When holding position is the right call

Keeping the application where it is can be the correct financial decision. It usually is when the application is stable, sits on a supported Windows Server and SQL Server, has no blocked features, and faces no audit pressure. A planned retirement inside two or three years is another good reason. Migration is an investment, and a system nearing the end of its life may not return it.

The comparison to bring to the meeting is two numbers: the yearly holding cost above, projected three years, and a migration estimate from an assessment. What a legacy .NET migration involves explains what drives the second number.