In ASP.NET, server-side pages are known as Web Forms. The original article describes them as web pages that contain server controls such as text boxes, drop-down lists, check boxes, and buttons—very similar in appearance to HTML forms, but with a server-side processing model. :contentReference[oaicite:4]{index=4}
A Web Form is requested by the browser, processed on the server by the ASP.NET runtime, and then rendered as HTML, CSS, and JavaScript back to the client. The user never sees the server-side code; they only see the generated markup.
The original content highlights a key distinction: HTML forms run entirely on the client, while ASP.NET Web Forms execute on the server. :contentReference[oaicite:5]{index=5} Beyond that, Web Forms add several important features:
@Page at the top of the file.
The following example shows a basic Web Form with a page directive and a few server controls:
<%@ Page Language="C#" AutoEventWireup="true"
CodeFile="Default.aspx.cs" Inherits="_Default" %>
<!DOCTYPE html>
<html>
<head runat="server">
<title>Sample Web Form</title>
</head>
<body>
<form id="form1" runat="server">
<asp:Label ID="lblMessage" runat="server"
Text="Hello from Web Forms!" />
<br />
<asp:TextBox ID="txtName" runat="server" />
<asp:Button ID="btnSubmit" runat="server"
Text="Submit"
OnClick="btnSubmit_Click" />
</form>
</body>
</html>
In the code-behind file, you can handle events such as btnSubmit_Click to process input, access
the server-side state of controls, and update the page before it is rendered to HTML.
The original article explains that a Web Form is first compiled into IL, not just the code-behind but “every control and element in the page.” This compiled IL is then executed by the Common Language Runtime (CLR). :contentReference[oaicite:6]{index=6}
Because IL is language-neutral, you can write your server-side logic in any .NET language that targets the CLR. The result is HTML output that can be displayed in any browser, making Web Forms language-independent and browser-independent from the user’s perspective.
Web Forms was designed for rapid application development at a time when server-side rendering and stateful controls were the norm. Today, many teams prefer patterns like MVC, Razor Pages, or SPA frameworks that provide clearer separation of concerns and better control over client-side behavior.
If you maintain an existing Web Forms application, understanding its compilation model, server controls, and page directives—as outlined in the original article—remains essential. If you plan new development, consider whether a more modern framework aligns better with your long-term maintenance and scalability goals.
An ASP.NET Web Form is a server-side page that combines markup and server controls. It runs under the .NET Framework, handles events on the server, and generates HTML for the browser. Developers typically work with both the .aspx file and a code-behind file.
A classic HTML form is parsed and executed solely by the browser. An ASP.NET Web Form, by contrast, is compiled and executed on the server, supports server controls, view state, and rich event handling, and then outputs HTML to the client.
Yes. Web Forms compile to IL and run on the CLR, so server-side logic can be written in any supported .NET language. The rendered output is standard HTML, which allows users on different browsers and platforms to use the application.
Web Forms is still supported for existing applications on the full .NET Framework, but new projects typically use ASP.NET Core MVC, Razor Pages, Blazor, or other modern web stacks that offer better testability, performance, and long-term support.