Using ToolkitScriptManager, but still receiving “AjaxControlToolkit requires ASP.NET Ajax 4.0 script

I’ve read all the posts with this same issue and have not been able to resolve it in my case.  Is the wrong version of the Toolkit being cached somewhere?
I upgraded my web application from 3.5 to 4.0 and am getting “AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced.” on pages that are using ToolkitScriptManager, not ScriptManager.
For example
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="test.aspx.cs" Inherits="Loogla.test1" %>
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
    

    
    
    

    
        
        
        
        Far
    
    
    
Version 4.1.40412.2 of AjaxControlToolkit.dll is in my bin folder and also referenced in my project.
I’m stumped at this point.

I’ve read all the posts with this same issue and have not been able to resolve it in my case.  Is the wrong version of the Toolkit being cached somewhere?

I upgraded my web application from 3.5 to 4.0 (VS 2008->2010) and am getting “AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced.” on pages that are using ToolkitScriptManager, not ScriptManager.

For example

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="test.aspx.cs" Inherits="Loogla.test1" %>
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>






    
Far

Version 4.1.40412.2 of AjaxControlToolkit.dll is in my bin folder and also referenced in my project.  Passing the error above, gives “Sys.Extended.UI is null or not an object”.

I’m stumped at this point.

Try creating a sample app and drop a toolkit  extender and cpl of controls and see if the problem persists.I believe there might be some problem with your config file /

People often throw around the word “Hero”.  Those like Karan actually deserve it.In my config file, i hadI changed it to and it worked like a charm.Incidentally, this also fixed another upgrade error I was having wherein the first load to the web  app produced a Security Exception when trying to reference “AjaxControlToolkit.ToolkitScriptManager”.  Hope this helps someone else.

Thanks buddy. Glad it worked for you.