In order to use any of the client functionality you have to ensure that the script libraries (jquery.js and ww.jquery.js) are loaded.

There are a number of ways this can be done:

  • Using one of the server side AJAX controls
    Any of the AJAX server controls in this control library will by default automatically load the jquery and ww.jquery into the page by using "WebResource" or "Default" as the value for ScriptLocation and jQueryScriptLocation. WebResource loads internally from resources while Default loads from the virtual's ~/scripts folder. If <head runat="server"> is set jQuery is embedded in the top of the header, ww.jquery at the bottom.

  • Using ScripContainer Control
    If you want more declarative control over script loading in the page you can load them via this control. The control works similar to standard <script src=""> links in a page, but the server side sees the src files and loads only single instances. These declarations are integrated and visible to other controls that also load these resources to ensure only a single script reference gets embedded in the page. If you want the control to override other control functionality place this control near the top of the page before other Ajax controls. ScriptContainer allows precise placement of script in the top of the header, bottom of header, inline or at inline position.

  • ControlResources.LoadjQuery/LoadwwjQuery
    If you don't have any of the control on the page you can force the server side to automatically load the script with: ControlResources.LoadjQuery() and LoadwwjQuery(); in your page code. This will load the library as a WebResource with GZIP compression (if available) and is preferred over directly linking the library in script code. Again this integrates with ScriptContainer and control based loading to avoid duplicate script loading.

  • Linking scripts directly
    Of course you can also link the script library directly into your HTML document via <script src="scripts/jquery.js" type="text/javascript"> as well as ww.jquery.js tags. This works fine but you need to make sure that any of the other server controls set their scrip locations to blank so that they don't automatically include the scripts again from resources.

Note that you can always override any default load action for script libraries by setting the script location properties and setting them to blank. This gives you full control over if and where the script libraries get loaded to allow for maximum flexibility when interacting with other scripts in the page.