Comments on: How you can force the Ajax Script Loader to use jQuery 1.4

By: Ricardo

Ricardo — Tue, 13 Jul 2010 22:57:53 +0000

Great post! By the way you can also add some shorcut to “onReady”, check this!

// Instruct the script loader to request
//  jQuery and jQuery Validate in the background,
//  The callback runs later, after both jQuery
//  and jQuery Validate have been loaded.
Sys.require([Sys.scripts.jQuery, Sys.scripts.jQueryValidate], function() {
  console.log("Loaded jQuery " + jQuery.fn.jquery);   
 });

By: Ryan Maloney

Ryan Maloney — Thu, 22 Apr 2010 12:59:25 +0000

Thanks for the fast response and the heads up on the future of start.js.

By: Dave Ward

Dave Ward — Thu, 22 Apr 2010 00:10:04 +0000

There’s a copy of start.js at this location:

http://ajax.microsoft.com/ajax/act/40412/start.js

Long-term, I think they’re focusing on a more generalized version of start.js’ script loader that would work easier in conjunction with jQuery or even be part of jQuery core. So, maybe not scraping it, so much as revamping it.

By: Ryan Maloney

Ryan Maloney — Wed, 21 Apr 2010 21:16:45 +0000

Do you know what happened to the script loader since the VS2010 release? I know the Ajax Library was merged with the control toolkit but there is no where on the microsoft cdn anymore to get a reference to start.js. I grabbed the toolkit source and it looks like they have a reference to start.js but it is buried in the site demo. I can’t find documentation anywhere. Is Microsoft scrapping this?

By: Dave Ward

Dave Ward — Thu, 11 Feb 2010 17:45:36 +0000

Personally, I've almost always used script elements. Going forward, I suspect I'll be using the script loader often. The patterns and practices "V.Next" web guidance is going to include a document that discusses methods for including scripts, and the sample application makes heavy use of the script loader (which led to discovering and finding solutions for interesting real-world problems around using it).

By: David Robbins

David Robbins — Thu, 04 Feb 2010 15:37:22 +0000

It seems to me that there are several pathways or approaches to encorporating jQuery into ASP.Net, whether it be MS Ajax with ScriptManager, a simple reference in your WebForm, etc. I’ve read your series for about a year now on different techniques and wondered if you considered putting a road map of the different approaches, and maybe links to the posts respective to each “style”? Maybe a permanent page?

Anyway, I enjoyed the post as always.

By: Dave Ward

Dave Ward — Mon, 01 Feb 2010 16:56:05 +0000

I agree that it should be consistent. I’m not sure why they chose to always use the CDN.

By: Robin Webb

Robin Webb — Mon, 01 Feb 2010 15:39:12 +0000

Thanks for your replies to my questions Dave – very useful.

I’m still not clear on why the start.js contains a hard coded reference to ajax.microsoft.com/ajax for jQuery when the other Microsoft libraries react to the location of start.js (local or CDN).

var ajaxPath = (window.location.protocol === "https" ? "https" : "http") + "://ajax.microsoft.com/ajax/";

Is this by design?

By: Dave Ward

Dave Ward — Mon, 01 Feb 2010 15:20:11 +0000

1. When the script loader injects a