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

By: leny

leny — Sat, 05 Feb 2011 04:25:26 +0000

or you can use the google.load() method, but if a new version it’s out and you’re comfortable using Sys.require([Sys.scripts.jQuery]); just edit and work with a local copy of star.js by the time you’re done with the app the final release of ms start.js should have the new stuff.
plus in development time you could even ad jquery UI like so..

 
     { name: "jQuery",
         releaseUrl: ajaxPath + "jquery/jquery-1.5.min.js",
         debugUrl: ajaxPath + "jquery/jquery-1.5.js",
         isLoaded: !!window.jQuery
     },          
     { name: "jQueryUI",
         releaseUrl: ajaxPath + "jquery.ui/1.8.9/jquery-ui.min.js",
         debugUrl: ajaxPath + "jquery.ui/1.8.9/jquery-ui.js",
         isLoaded: !!window.jQuery
     },

http://l3ny.com/chrome.jpg

@l3ny

By: Dave Ward

Dave Ward — Wed, 06 Oct 2010 17:59:52 +0000

It’s okay to use the // address, just specify the full jQuery version instead of “1″.

By: light and simple

light and simple — Wed, 06 Oct 2010 17:44:38 +0000

Thanks, Dave. Very comprehensive explanation. I want an approach I can use without thinking too much about it. I found the “//” solutions to URLs very useful in SSL and want the same kind of blanket approach for jQuery CDN linking. What do you suggest then?

By: Dave Ward

Dave Ward — Wed, 06 Oct 2010 17:28:47 +0000

You should never use the “latest version” URL. It only sets a 1 hour expires header instead of 1 year. For repeat visitors, that’s probably even slower than hosting jQuery on your local server. See more here:

http://encosia.com/2010/09/15/6953-reasons-why-i-still-let-google-host-jquery-for-me/

http://paulirish.com/2009/caching-and-googles-ajax-libraries-api/

By: light and simple

light and simple — Wed, 06 Oct 2010 16:53:39 +0000

Use this script link:

 src="//ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>

Omitting the protocol and jQuery version will give you SSL compatibility + latest version. Google also provides the jQuery UI and jQuery UI themes which you can link to in the same fashion in terms of omitting protocol and version to always have the latest version. I haven’t run into a situation yet where using a script loader was necessary as it increases overhead.

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