
380
❘
CHAPTER 13 THE CLIENT OBJECT MODEL AND JQUERY
The fi rst method is to just include the script tags, like you saw previously, directly to the page or,
even better, to the master page. You would need to ensure that no other components also add a ref-
erence to the jQuery library. Here, the term “components” refer to anything that may inject code
when the page renders, such as Web Parts. This is an acceptable approach if you control the entire
page, but many times this is not possible due to the modular nature of SharePoint development.
The next approach is to use the
ScriptLink control. The ScriptLink control will ensure that the
script is loaded only once and will also ensure that other dependencies have been loaded fi rst. Add
the following
ScriptLink server-side tag to your page to load the jQuery library:
<SharePoint:ScriptLink ID=”SPScriptLink”
runat=”server” Defer=”false”
Localizable=”false” Name=”jquery-1.4.2.js “>
</SharePoint:ScriptLink>
The ScriptLink control requires that you put the jQuery library fi le in the LAYOUTS directory, C:\
Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\
LAYOUTS
. This may not be possible if you have limited rights to the server, such as when you are
creating sandboxed solutions. Also, even if the JavaScript library is in the
LAYOUTS folder, the
ScriptLink control is not allowed to run as a sandboxed solution. T ...