Without ScriptManagerProxy, you couldn??™t have
the required scripts handled automatically for you because this was all in the content
page.
Introducing the UpdatePanel Control
In typical ASP.NET 2.0 applications, if you do a postback on the web page, the entire page
will be rerendered. This causes a ???blink??? or a ???flash??? in the client or browser. On the
server, the postback is detected, which triggers the page life cycle. This ends up raising
the specific postback event handler code for the control that caused the postback, and
this calls upon the page??™s event handler.
When you use UpdatePanel controls along with a ScriptManager control, you eliminate
the need for a full-page refresh. The UpdatePanel control is similar to a ContentPanel control
in that it marks out a region on the web page that will automatically be updated
when the postback occurs (but without the aforementioned postback behavior on the
client). It instead communicates through the XMLHttpRequest channel??”in true AJAX style.
The page on the server still handles the postback as expected and executes, raising event
handlers, and so on, but the final rendering of the page means that only the regions specified
in the UpdatePanel control??™s regions are created.
Pages:
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169