This Infragistics control requires a ScriptManager object on the page in order to operate correctly

Alistair asked on May 13, 2010 4:17 PM

Hi,

I have the following set-up:

A master page with a script manager on it.

A contentpage derived from the master page, which has a userControl on it.

The userControl has a WebDialog contol on it.

When I try to view the page, I get the message “This Infragistics control requires a ScriptManager object on the page in order to operate correctly”.

I tired to:

Add a scriptmanagerproxy to the control – got the same message
Add a scriptmanagerproxy to the content page – same message
Remove the scriptmanager from the master page and just add it to the content page – got the same message
Remove the scriptmanager from the master page and just add it to the usercontrol – got the same message

Any help you can offer would be very much appreciated.

Regards

Alistair

Replies

0

Alex Kartavov answered on Nov 20, 2008 12:39 PM

I believe the master page should have ScriptManager and the user control

should have ScriptManagerProxy on it. Let us know if it still does not

work this way. Thanks!
- 0
  
  Alistair answered on Nov 21, 2008 10:42 AM
  
  Unfortunately that didn't work… Same message as before.
- 0
  
  ustes answered on Jan 21, 2009 3:21 PM
  
  is there something missing when this happens? I mean something configured wrong, etc. I have a Mastpage with a Script manager, the Content pages are in an updatepanel, when I put a scriptmanagerproxy on the user control that is used on the default page I still get this error. Any help would be appreciated.
- 0
  
  Jim answered on Mar 13, 2009 10:41 PM
  
  I am having the same issue. Although I don't have a script manager on my Master Page I have it directly on the page I am working with and I still get this error. This Infragistics control requires a ScriptManager object on the page in order to operate correctly.
  
  I/we would appreciate any advice or help we can get.
  
  Jim
  - 0
    
    Harlow answered on May 19, 2009 10:31 PM
    
    I also have this issue.
    
    'This Infragistics control requires a ScriptManager object on the page in order to operate correctly.'
    
    I have a ScriptManager on the master page, a ScriptManagerProxy on the UserControl, and a WebDialogWindow on the UserControl.
    
    I am targeting .NET Framework 3.5.
  - 0
    
    Alex Kartavov answered on May 19, 2009 11:01 PM
    
    Tried it out in a sample seems to work…
    
    Here is my master page:
    
    <%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>
    
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    
    <html xmlns="http://www.w3.org/1999/xhtml">
    
    <head runat="server">
    
        <title></title>
    
        <asp:ContentPlaceHolder id="head" runat="server">
    
        </asp:ContentPlaceHolder>
    
    </head>
    
    <body>
    
        <form id="form1" runat="server">
    
        <div>
    
            <asp:ScriptManager ID="ScriptManager1" runat="server">
    
                </asp:ScriptManager>
    
                Master page
    
            <asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server">
    
    
    
            </asp:ContentPlaceHolder>
    
        </div>
    
        </form>
    
    </body>
    
    </html>
    
    Here is the content form:
    
    <%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default2.aspx.cs" Inherits="Default2" MasterPageFile="~/MasterPage.master" %>
    
    <%@ Register Assembly="Infragistics35.Web.v9.1, Version=9.1.20091.2013, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"
    
          Namespace="Infragistics.Web.UI.LayoutControls" TagPrefix="ig" %>
    
    <%@ Register src="WebUserControl.ascx" tagname="WebUserControl" tagprefix="uc1" %>
    
    <asp:Content ID="q" ContentPlaceHolderID=ContentPlaceHolder1 runat=server>
    
          <asp:ScriptManagerProxy ID="ScriptManagerProxy1" runat="server">
    
    </asp:ScriptManagerProxy>
    
    <ig:WebDialogWindow ID="WebDialogWindow1" runat="server" Height="300px" Width="400px">
    
    </ig:WebDialogWindow>
    
          <uc1:WebUserControl ID="WebUserControl1" runat="server" />
    
    
    
    </asp:Content>
    
    Here is the user control:
    
    <%@ Control Language="C#" AutoEventWireup="true" CodeFile="WebUserControl.ascx.cs" Inherits="WebUserControl" %>
    
    <%@ Register Assembly="Infragistics35.Web.v9.1, Version=9.1.20091.2013, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"
    
          Namespace="Infragistics.Web.UI.LayoutControls" TagPrefix="ig" %>
    
    <asp:ScriptManagerProxy ID="ScriptManagerProxy1" runat="server">
    
    </asp:ScriptManagerProxy>
    
    <ig:WebDialogWindow ID="WebDialogWindow1" runat="server" Height="300px" Width="400px">
    
    </ig:WebDialogWindow>
    
    Everything seems to be ok.
    
    Could you share a simple sample? Thanks!
  - 0
    
    Harlow answered on May 19, 2009 11:10 PM
    
    Unfortunately, it seems to work in a simple example, but not in my existing application which is quite complex.
    
    I did not have this problem before switching from .NET 2.0 to .NET 3.5. The exact same code worked in 2.0, but now I get this error in 3.5. All other functionality, (Ajax, UpdatePanels, WARP panels, other Infragistics controls, etc.) are working fine. The only problem I see is with the WebDialogWindow.
    
    When I remove the WebDialogWindow, the error goes away. I do not get the error from any other Infragistics controls on the UserControl (UltraWebGrid, UltraWebGridExcelExporter, WebDateChooser).
    
    Is there another Infragistics control you can suggest I can try to put on the UserControl to see if it is just with the WebDialogWindow control that has the problem?
  - 0
    
    Alex Kartavov answered on May 19, 2009 11:22 PM
    
    Try any of the new controls – WebImageViewer, WebSplitter, WebDataGrid…
    
    It may be also possible that the Visual Studio is pulling caching tricks on you.
  - 0
    
    Harlow answered on May 20, 2009 12:22 AM
    
    Okay, I found the problem. It looks like the Project Upgrade Wizard did not work completely (maybe a Source Control issue). I manually replaced some Infragistics2 references with Infragistics35 references and it works now.
    
    It was hard to find this since most of the older Infragistics controls didn't seem to care that they were 2.0 assemblies loded into a 3.5 environment, only the newer controls were picky about it.
    
    Thank you for your help.
  - 0
    
    Federico answered on May 13, 2010 4:17 PM
    
    1 script manager in the master page, and 1 script proxy in the content page and all sorted (as it is shown in the aspx published above, thanks alexander for your clear and straight forward code). Just make sure to put the script manager and proxy before the controls.
    
    good luck!.