• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2104
  • Last Modified:

ScriptManagerProxy and MasterPages

Greetings 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
0
allanmark
Asked:
allanmark
  • 6
  • 5
1 Solution
 
cdaly33Commented:
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?
0
 
allanmarkAuthor Commented:
Page does run.
0
 
cdaly33Commented:
What is the remaining issue?  If the page runs then .net is correctly picking up your scriptmanagerproxy.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
allanmarkAuthor Commented:
Please see atatched Jpg.

How do I clear this up?
Err.jpg
0
 
cdaly33Commented:
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\Framework\v2.0.50727\Temporary ASP.NET Files\".  Just delete the project for that folder and reopen the project.
0
 
allanmarkAuthor Commented:
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??!!


   

0
 
cdaly33Commented:
Are all the issues resolved?
0
 
allanmarkAuthor Commented:
No.

If the MasterP{age has a ScriptManager, you wouldn't need to add a SCriptManagerProxy to it.

Without a valid ScriptManagerProxy on the Content page, I can't add an UpdatePanel -- which I need to do!!

0
 
cdaly33Commented:
I'm not sure why you need an update panel on the Content page.  Normally having a ScriptManager or ScriptManagerProxy in the Masterpage is good enough.  I've never needed to add them anywhere except the Masterpage.
0
 
allanmarkAuthor Commented:
For this particular application, the requirements are very diferent for each of several page, which happen to have a similair layout (hence the MasterPage).
0
 
allanmarkAuthor Commented:
An answer!!

      <system.web>
            <pages>
                  <controls>
                        <add tagPrefix="ASP" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

CHANGED TO

                        <add tagPrefix="ajaxext" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
0
 
navyjax2Commented:
Didn't work for me.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now