http://blogs.msdn.com/jorman/archive/2007/05/18/referencing-js-files-for-the-ajax-control-toolkit.aspxI was recently working with someone that was leveraging the AJAX Extension and the Control Toolkit and they were running into an issue where a customer's environment was causing issues making requests to ScriptResource.axd. Since they couldn't changeen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jorman/archive/2007/05/18/referencing-js-files-for-the-ajax-control-toolkit.aspx#2973911Tue, 29 May 2007 22:56:19 GMT91d46819-8472-40ad-a661-2c78acb4018c:2973911Spot<p>This won't work for the AjaxControlToolkit.ExtenderBase.BaseScripts.js file. It will be missing the JSON'd ScriptResources section at the bottom. Take a look at the differences in Fiddler when you specify a ScriptPath and when you don't. </p> <p>For some reason when the script is served up with ScriptResource.axd those resource strings will get JSON'd at the end of the AjaxControlToolkit.ExtenderBase.BaseScripts file. The AjaxControlToolkit.ExtenderBase.BaseScripts.js file in the obj will not have those resource strings. Causes major breakage with Calendar and other AJAX controls that depend on those strings.</p> <p>I solved the problem by looking at the AjaxControlToolkit.ExtenderBase.BaseScripts.js file that was being served with fiddler, and then appended the JSON'd resource strings to the bottom of the AjaxControlToolkit.ExtenderBase.BaseScripts.js file that I copied from the obj directory. Now everything is working.</p>