Ajax Control Toolkit 40412 seems to be using its own customized version of MicrosoftAjax.js and MicrosoftAjaxWebForms.js. Toolkit's version is 4.1.40412.2, while the version that come with ASP.NET Ajax 4 is 4.0.30205.0, and the Toolkit does NOT work with the ASP.NET Ajax 4 version. By default when using the toolkit the version is swapped to the toolkit's version.
While the ASP.NET Ajax 4 version is hosted on the CDN (http://www.asp.net/ajaxlibrary/CDNAjax4.ashx) the version with the Toolkit is not (http://www.asp.net/ajaxlibrary/CDNACT40412.ashx), which doesn't make any sense because all the other files are hosted. Therefore, a CDN version of MicrosoftAjax.js and MicrosoftAjaxWebForms.js is UNAVAILABLE when using the Ajax Control Toolkit 40412.
The new attribute EnableCdn="true" is of course rendered completely useless when using the Ajax Control Toolkit because the idea is that the MicrosoftAjax.js and MicrosoftAjaxWebForms.js files would then be linked by references to the CDN. This does not happen with the Toolkit because as described the Toolkit replaces the those files with its own. I was very surprised to find out that all my excitement about having CDN support was made void when I included the Toolkit in my project.
A possible solution would be to add the following to the global.asax.cs file:
void Application_Start(object sender, EventArgs e)
ScriptManager.ScriptResourceMapping.AddDefinition("MicrosoftAjax.js", new ScriptResourceDefinition
Path = "~/Scripts/MicrosoftAjax.js",
DebugPath = "~/Scripts/MicrosoftAjax.debug.js",
CdnPath = "http://ajax.microsoft.com/ajax/4.0/1/MicrosoftAjax.js",
CdnDebugPath = "http://ajax.microsoft.com/ajax/4.0/1/MicrosoftAjax.debug.js"
This of course is not helpful as the files, as stated earlier, for the toolkit are NOT on the CDN.
Thanks in advance for any help in solving this issue,