Menu
I don't think I've been able to find a definitive answer on this, so I'll ask it here. When is a ScriptManager (or ScriptManagerProxy in the case of using a ScriptManager on a Master Page) needed?
For example, let's say that I have a ScriptManager on a MasterPage:
If I have a Web Content Form that contains an UpdatePanel, does it need a ScriptManagerProxy?
If I have a Web Content Form that contains a User Control and that User Control has an UpdatePanel in it, does the User Control need a ScriptManagerProxy?
If I have a Web Content Form that contains an UpdatePanel and a UserControl that also contains an UpdatePanel, does the Web Content Form and/or the User Control require a ScriptManagerProxy?
Thanks.
546
ScriptManager is a server-side control that sits on your Web Form and enables the core of ASP.NET AJAX. Its primary role is the arbitration of all other ASP.NET AJAX controls on the Web Form and the addition of the right scripting libraries to the Web browser so that the client portion of ASP.NET AJAX can function.
I would put the ScriptManager at the top of the Master page outside of any Multi-View. The ScriptManager is a what is used by the Microsoft controls to provide AJAX functionality.
Introduction. The ScriptManager control is central to Ajax functionality in ASP.NET. The control manages all ASP.NET Ajax resources on a page. This includes downloading Microsoft Ajax Library scripts to the browser and coordinating partial-page updates that are enabled by using UpdatePanel controls.
A page can contain only one ScriptManager control in its hierarchy.
ScriptManagerProxy enables a content page to pass references to the ScriptManager placed on its ASP.NET master page.
Here is an asp.net video: http://www.asp.net/Learn/ajax-videos/video-95.aspx
Thanks
Joe
87
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
