ASP.NET Web Forms support: keep the application secure while you plan what is next
We maintain ASP.NET Web Forms and .NET Framework 4.x applications on a monthly retainer: security updates, dependency upgrades, bug fixes and small changes. When you are ready, we migrate them to modern .NET section by section.
Resolved in 14 minutes. Your team slept through it.
Why it matters now
Web Forms is not going away overnight. .NET Framework 4.8 and 4.8.1 are supported as part of Windows for the life of the Windows version they run on, so a well-patched Web Forms application on a supported server can stay secure. What it does not get is new features, and fewer developers want to work on it every year.
The real risks are around the code: NuGet packages years out of date, a jQuery version with known vulnerabilities, ViewState and session settings nobody has reviewed, and a single developer who understands the build. We take those on first, then give you an honest view of whether and when to migrate.
Signs you need this
Only one developer can build and deploy the application
.NET Framework and Windows updates applied monthly, emergency fixes within your SLA.
02
Dependency upgrades
NuGet packages, jQuery and client libraries upgraded to supported versions, tested before release.
03
Bug fixes and small changes
From a monthly bank of hours, released through a repeatable, documented build.
04
Build and deploy
The application put under version control with a scripted build, so releases stop depending on one laptop.
05
Security review
ViewState, authentication, session and error-handling settings reviewed and fixed.
06
Migration readiness
An assessment of which sections would move easily to modern .NET and which need rework.
Patching cadence
Critical security fixesWithin the SLA response time for your tier
.NET Framework and Windows updatesMonthly
NuGet and client library reviewQuarterly
Penetration-test findingsFixed and documented on an agreed schedule
Security posture
Named-user access only, through your VPN, jump host or SSO
Credentials stored in a vault, never in email or tickets
Every change logged against a ticket, with a rollback step
NDA and data processing agreement before any access
Findings from your penetration tests fixed and documented
Service levels
Written into the contract. Mix tiers across your estate according to how critical each system is.
Example service levels by support tier
Essential
Business
Mission-critical
Critical (site down)
4 hours
1 hour
15 minutes
High (major feature broken)
Next business day
4 hours
1 hour
Normal
3 business days
1 business day
4 hours
Cover hours
Mon–Fri, business hours
7am–10pm, 7 days
24/7/365
Uptime target
99.5%
99.9%
99.95%
Named engineers
1
2
Dedicated team
How the takeover works
Weeks 1–2
Audit
Read-only access under NDA. Versions, risks, costs and a quote.
Weeks 3–4
Knowledge transfer
Runbooks, credentials vault and handover sessions with your current team or vendor.
Month 2
Stabilise
Urgent patches, monitoring and backups in place before anything else changes.
Ongoing
Run & improve
SLA-backed support, planned upgrades and a monthly report.
Free estate audit · 2 weeks
Get a written report on your ASP.NET Web Forms estate.
Read-only access, under NDA. Versions, end-of-support dates, security findings and a monthly quote. Keep the report either way.
ASP.NET Web Forms support: questions, answered
Should we migrate off Web Forms now?
Not always. If the application is stable, rarely changes and runs on a supported server, keeping it secure can be the right call for now. If it changes often, or hiring for it is hard, a staged migration usually pays back.
Can you support Classic ASP too?
Yes. Classic ASP still runs as an IIS component on supported Windows Server versions, and we maintain it on the same terms.
Do you need the source code?
Ideally. If only compiled binaries survive, we can usually decompile enough to support and rebuild the application, and we tell you early what that involves.
Palm Leaves