Web Forms页面对象是否内存持久化？ViewState使用疑问
Hey Jacob, great question—Web Forms can feel a bit counterintuitive at first when you’re coming from other C# development contexts, so let’s break this down clearly.
First: Clarifying the Page Object’s Lifecycle
Let’s start with a key correction: The System.Web.UI.Page object is not persistent across requests. Every time a user interacts with the page (clicks a button, submits a form, even refreshes), the server creates a brand new instance of your Page class to handle that request. Once the response is sent back to the browser, this instance is immediately destroyed. Any values stored directly on the Page object will be lost once the request finishes.
ViewState doesn’t rely on a server-side identifier for the Page instance—instead, it serializes state data into a hidden HTML field (__VIEWSTATE) that’s sent to the client. On subsequent postbacks, this data is sent back to the server, which deserializes it to restore the page’s state for the new Page instance.
Can You Use this to Reference Page Properties/Methods During Events?
Absolutely! When you’re inside a page event handler (like Page_Load, Button_Click, or any custom event you’ve defined), this refers directly to the current Page instance handling the ongoing request. You can freely use this to access:
- Built-in Page properties (e.g.,
this.Title,this.IsPostBack) - Server controls on the page (e.g.,
this.MyTextBox.Text,this.MyGridView.DataBind()) - Custom methods or properties you’ve added to the Page class (e.g.,
this.CalculateCartTotal())
This works seamlessly because you’re operating within the context of the current request’s live Page instance.
When Should You Use ViewState?
ViewState exists specifically to preserve data across postbacks (since the Page instance is recreated every time). Use it in these scenarios:
- You need to retain a temporary value that doesn’t come from a control’s built-in state (e.g., a calculated result, a user’s filter selection that you don’t want to re-compute on every postback)
- You want to preserve custom state for a control that doesn’t handle its own state (most standard Web Forms controls use ViewState by default for core state, like a CheckBox’s checked status)
- You need to pass data between requests without relying on server-side session state (which ties data to a user’s session) or visible query strings
Critical ViewState Caveats:
- Avoid large datasets: ViewState adds to the size of your rendered HTML page. Storing big chunks of data here will slow down page load times and increase bandwidth usage.
- Don’t store sensitive data: Since ViewState is sent to the client (and can be decoded by savvy users), never put confidential information like passwords or user IDs in it.
内容的提问来源于stack exchange，提问作者Jacob
