I am attempting to use the Calandar Extender from the latest AjaxControlToolkit, the beta one found at http://ajax.codeplex.com.

After adding it to my module and viewing a page with the module on it I receive the following error:

AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the AjaxScriptManager in System.Web.Ajax.dll, or use the ToolkitScriptManager in AjaxControlToolkit.dll.

I have used the ScriptManager and the AjaxScriptManager in standalone websites...  I have also use some ajax componenets in DotNetNuke websites and understand that DotNetNuke handles the registration of the script manager.  I have made sure to use the following code in my user control to tell DNN to register it's script manager:

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
If Not IsPostBack Then If DotNetNuke.Framework.AJAX.IsInstalled Then End If

I continue to receive the error and that makes me wonder, how do I show DotNetNuke which script manager it should be registering, so that I can get the AJAX 4.0 code correctly involved?

Any help is appreciated!

Matt Christenson

DotNetNuke.Framework.AJAX.RegisterScriptManager()

The link that you provided took me to a page to download ASP.NET Ajax Library Beta 0911, which is the one that I have been using.  While it's called beta, it's also considered 'stable' and seems to be used by many.

I was able to resolve my issue by finding the prior version of the .dll

The version that works is : 3.0.30930.28736

The version that did not work was : 3.0.31106.0

This does pose the question though, if for some reason I did want to use the newer assembly, is there a way that the core DNN product can be configured to use a different class as it's script manager?  apperently simply overwritting the .dll in the /bin folder with the latest version was not enough.

Thank you for your help!

Matt Christenson