Page does run.
Main Topics
Browse All TopicsGreetings all,
I have an Ajax-enabled web ap. Each MasrePage created has by default a ScriptManager on it.
On the content pages I would like to make use of UpdatPanels. I dragged a ScriptMangerProxy to the page (inside the ContentspLaceHolder) but get an error, "Element 'ScriptManagerProxy' is not a known element. This can occur if there is a compilation error in the Web site (there are no errors, prior to adding the scriptmanageproxy.
1. What am I missing?
2. Also, if there are 2 contentplaceholders o Masterpage, then I will need one
scriptprooxymanager inside each of those, on the content page - is this correct?
In advance, thanks?
allanmark
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for the pic. That does help. My first idea is what happens when you just put the scriptmanagerproxy in the masterpage? In the past when VS has had trouble picking up the tags I've closed down VS and deleted the temp asp.net compilation files. These would normally be located in "c:\Windows\Microsoft.NET\
Ok.
I closed down the app, deleted the folder, re-opened the app and added the SCriptManagerProxy - same thing.
Your first idea - added the proxy to the MasterPage -- worked:
<div id="header">
<!-- Header start -->
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<asp:ScriptManagerProxy ID="ScriptManagerProxy1" runat="server">
</asp:ScriptManagerProxy>
...................
....................
NOTE THE ID TAG WHICH WASN"T PRESENT WHEN I ADDED TO THE CONTENT PAGE??!!
An answer!!
<system.web>
<pages>
<controls>
<add tagPrefix="ASP" namespace="System.Web.UI" assembly="System.Web.Exten
CHANGED TO
<add tagPrefix="ajaxext" namespace="System.Web.UI" assembly="System.Web.Exten
Business Accounts
Answer for Membership
by: cdaly33Posted on 2009-03-30 at 13:19:57ID: 24022894
First, a ScriptManagerProxy should only appears once during the rendering of a page. Therefore, if you have one in your MasterPage then that should be plenty.
The issue of "Element 'ScriptManagerProxy' is not a known element" error could be a bunch of stuff. Does the page run?