From Web Forms Events to Explicit Request Flows

Web Forms made it easy to start building quickly. A page could contain controls, code-behind, and event handlers, and the framework carried state between requests. That convenience also made the real request flow difficult to see.

The hidden path

In a mature Web Forms application, a button click might depend on ViewState, page lifecycle events, control IDs, validation order, and code running in a base page. The visible button was only the last step in a much longer path.

MVC changed the vocabulary. A request had a route, an action, a model, and a response. That did not automatically make the code good, but it made the boundaries inspectable.

The translation pattern

The useful migration pattern was:

control event
  -> route + HTTP verb
  -> request model binding
  -> validation
  -> service or data operation
  -> view, partial view, or JSON response

The controller action became the place where the HTTP contract was visible. The service became the place where reusable business behaviour could live. The view became a representation of the result rather than a second controller.

Why partial views matter

Not every action needs to return a full page. CDIS uses partial responses for modal forms, table refreshes, and small sections of a page. That is the MVC equivalent of updating part of a Web Forms page, but the update target is now explicit in the markup and the response.

The trade-off is that the developer must understand the client-side contract: which element is replaced, whether validation is reattached, and whether a parent table or modal needs a follow-up action.

A better debugging method

When a migrated feature misbehaves, trace it in this order:

1. Identify the URL and HTTP method.
2. Find the controller action.
3. Check model binding and ModelState.
4. Follow injected services and database calls.
5. Confirm the response type.
6. Inspect the view or JavaScript code that consumes the response.

This is more reliable than starting at the button and guessing which old page event might have fired.

The lesson

The biggest improvement from Web Forms to MVC was not a new syntax. It was the ability to name the stages of a request. Once those stages were visible, the application could be tested, logged, secured, and gradually refactored without requiring every change to understand the entire page lifecycle.