Working with ASP.NET?

ASP.NET app refusing to start or impossible to touch? We take it on.

A lot of ASP.NET work that lands on our desk is a web app that quietly earned its keep for ten or fifteen years, and whichever team built it has long since dispersed. We work out what the thing actually does, write that down, and keep it serving customers while any real upgrade happens on the side.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

aspnet.log

still failing

What it is

ASP.NET at a glance

ASP.NET is Microsoft's web framework, first shipped in 2002 as part of the original .NET Framework. Over the years it grew several faces: Web Forms in 2002, MVC in 2009, WebAPI in 2012, Razor Pages, and SignalR for pushing updates to browsers in real time. Each one owns a slice of the production code still running today.

ASP.NET Core, introduced in 2016, is a complete rebuild of the framework on cross-platform .NET Core and the later unified .NET. The modern line sits on .NET 8 LTS and offers Minimal APIs, Razor Pages, Blazor Server and WebAssembly, SignalR, and gRPC. Meanwhile the old Framework-era ASP.NET still carries huge amounts of business code, Web Forms especially.

Type
Web framework for .NET
First released
2002
License
MIT for ASP.NET Core; proprietary for classic ASP.NET on .NET Framework
Maintained by
Microsoft and the .NET Foundation
Typically used for
Enterprise web apps, internal tooling, APIs, line-of-business apps, SignalR-based realtime

The honest version

ASP.NET pros and cons

No technology is all upside. This is where ASP.NET earns its place and where it tends to cause trouble.

Where ASP.NET is strong

  • Twenty-plus years of production useClassic ASP.NET on Windows has been carrying critical web workloads since the early 2000s, which means hiring, hosting and documentation are all plentiful.
  • Serious throughput on ASP.NET CoreKestrel running on Linux routinely posts benchmark numbers near the top of the field, and teams get that performance without writing any low-level code.
  • Pick the model that suits the jobMVC for traditional server-rendered pages, Razor Pages for simpler flows, Blazor for interactive components, and Minimal APIs for small services all live under one roof.
  • Dependency injection is in the boxASP.NET Core ships with a first-class DI container, so wiring services together no longer needs a separate library or a hand-rolled factory layer.
  • ASP.NET Identity for loginsA complete membership system covers password hashing, roles, external providers and multi-factor sign-in without reaching for a third-party package.
  • SignalR for live updatesPushing changes from server to connected clients over WebSockets is a few lines of code, which keeps dashboards and chat features out of ad-hoc polling territory.
  • Deep IIS integration on WindowsClassic ASP.NET and ASP.NET Core both hook into IIS for Windows authentication, HTTPS certificates and process hosting, which fits cleanly inside most corporate networks.
  • Strong tooling across editorsVisual Studio, JetBrains Rider and VS Code all handle ASP.NET projects well, with hot reload, Razor language support and integrated profilers.

Where ASP.NET bites

  • Two products share a confusing nameClassic ASP.NET on .NET Framework and ASP.NET Core on modern .NET are genuinely different stacks that happen to carry the same brand, which trips up new hires every time.
  • Web Forms does not port to CoreAny app built on the postback-and-viewstate model needs a redesign onto MVC, Razor Pages or Blazor rather than a straight recompile, so these upgrades are rewrites in practice.
  • WebAPI 2, Core API and Minimal APIs look alikeThree generations of HTTP endpoint style sit side by side, with different routing, filters and lifetimes, and old samples online still point newcomers at the wrong one.
  • ASP.NET Identity keeps changing shapeThe schema has shifted across versions, so upgrading a long-lived app often means writing migrations to bring a legacy users table forward into the current layout.
  • IIS brings its own operational taxApp pool recycling, worker process isolation, module ordering and web.config inheritance all affect behaviour, and misconfiguration shows up as errors that rarely match the real cause.
  • Blazor WebAssembly ships a large payloadThe runtime and app assemblies download to the browser on first visit, which costs megabytes of transfer and seconds of startup compared with a plain server-rendered page.
  • Old Web Forms apps are untouchable in practiceTen- or fifteen-year-old ASPX codebases, with code-behind files and server controls everywhere, are common in production and nobody on the current team wants to open them.

Sound familiar?

Common ASP.NET problems we fix

The ASP.NET problems that bring people to us, and what you have once each one is fixed.

HTTP 500.30 · ANCM start failure

The ASP.NET Core app will not start behind IIS

The ASP.NET Core Module reports in-process startup failed, usually from a missing runtime, a bad connection string, or an exception thrown during host build.

Boots cleanly on every restart

Web Forms · .aspx code-behind

A Web Forms app needs to move onto ASP.NET Core

Postbacks, viewstate and server controls do not carry over, so the move is a redesign onto MVC or Razor Pages rather than a recompile.

Modern stack, same business rules

last commit: 2019 · author departed

An ASP.NET MVC app came from a team that is gone

Controllers, views and a service layer of unknown shape, builds that only ran on one laptop, and no written record of how it releases.

Reproducible build, documented app

viewstate 2.4 MB · GridView

Pages are slow and the viewstate is enormous

Classic Web Forms controls round-tripping thousands of rows on every postback, dragging down even fast connections.

Fast pages, viewstate under control

WebAPI 2 · Owin

The WebAPI 2 service needs a modern replacement

An HTTP API hosted on the old Framework pipeline that is holding back the upgrade of everything around it.

Reimplemented on ASP.NET Core

pool recycles every 29 hours

The IIS app pool keeps restarting

Default recycle timers, memory thresholds or unhandled background exceptions sending the worker process down and taking in-flight requests with it.

Pool stable, cause understood

no handler for scheme 'Cookies'

Logins fall over after a framework upgrade

Authentication wiring that worked under the old middleware order no longer registers correctly under the new one.

Users sign in without surprises

EF: provider failed on Open

The app cannot reach its database

Entity Framework opens a connection that the database rejects, from a stale password, firewall change or connection string that points at the wrong environment.

Data layer connected and tested

What we do

ASP.NET help, from rescue to upkeep

Call us for one broken deploy, or hand us the whole app.

Rescue
Sites throwing 500.30, pages going yellow, pools recycling every hour. We get it serving again before we look for the cause.
Web Forms to ASP.NET Core
Planned redesigns off Web Forms onto Razor Pages or MVC, built on a branch and cut over only when it passes the same tests as the old one.
MVC takeover
Inheriting an ASP.NET MVC codebase from a previous team, reproducing the build, writing the missing notes and taking release day off their hands.
WebAPI 2 to modern APIs
Reimplementing legacy WebAPI 2 endpoints on ASP.NET Core with Minimal APIs or controller-based routing, keeping the contracts intact.
Performance
Kestrel and Core profiling, viewstate cleanup, EF query review and sensible caching, with numbers before and after.
Managed Tech
Framework and dependency updates, IIS and Kestrel tuning, health checks on the app, and an engineer who already knows the solution when a deploy misbehaves.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running ASP.NET alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

ASP.NET questions

Something else? Call+1 737 727 7327

Can you migrate our ASP.NET Web Forms app to ASP.NET Core?

Yes, though it is a redesign rather than a port. Web Forms, postbacks and server controls have no direct equivalent in ASP.NET Core, so the pages move onto Razor Pages, MVC or Blazor depending on the interactivity each screen needs. We read the existing app first, agree the target per screen, and run the rebuild on a branch alongside the live site until it passes the same tests.

What's the modern replacement for ASP.NET WebAPI 2?

ASP.NET Core, usually as controller-based APIs for anything that already uses attribute routing, or Minimal APIs for small services and internal endpoints. We keep the public contract of each route the same, swap the hosting and dependency injection underneath, and run both old and new side by side until callers are confirmed happy.

Can you take over an ASP.NET MVC application from a previous team?

Yes, and it is one of the most common things we do. We take the repository, reproduce the build on a clean machine, document the release process, and leave you with an application a second engineer can safely touch. If it also needs a framework upgrade, that becomes the next phase rather than a surprise.

Why does our ASP.NET Core app crash on startup with 500.30?

500.30 is the ASP.NET Core Module reporting that the app threw during host build. The usual causes are a missing runtime on the server, a configuration value that is null when the app tries to read it, a database that cannot be reached during warmup, or a DI registration that throws. The stdout log the module writes points at the real stack trace within a few minutes.

Should we stay on ASP.NET Framework 4.8 or move to .NET 8?

New work should start on .NET 8 without question. For an existing Framework 4.8 app the answer depends on what it is built from. A clean MVC or WebAPI 2 codebase ports in weeks; a Web Forms codebase is a redesign measured in months. We read the app, give you a sized plan, and you decide whether to port now, port in phases, or leave it in maintenance.

Free estimate

ASP.NET giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.