Proper way of bringing in jQuery into ASP.NET (or any other external JavaScript)

Question

What is the difference between those three code samples here below? Is one better than the others and why?

1.Page.ClientScript.RegisterClientScriptInclude(typeof(demo), "jQuery", 
                                                ResolveUrl("~/js/jquery.js"));

2. 
<asp:ScriptManager runat="server">
    <Scripts>
      <asp:ScriptReference Path="~/jquery-1.2.6.min.js" />
      <asp:ScriptReference Path="~/jquery.blockUI.js" />
     </Scripts>
  </asp:ScriptManager>

3. <script type="text/javascript" src="/js/jquery.latest.js"></script>

I've seen people using jQuery in their examples, and each one of them brings jQuery into ASP.NET in a different way. What is the best way?

TStamper · Accepted Answer · 2009-04-15 17:36:24Z

2

The first one is

used on server side for adding client script

The second one is

used with managing of asp.net AJAX scripts.If jQuery detects an ASP.Net AJAX ScriptManager, it will use this to register the scripts instead of Page.ClientScript

The third one is

the plain way to register the jquery plugin

I typically prefer the last one over the second one, but I never use Ajax anyway, and the first it only needed when you want to add in script after a postback to the server is done

edited Apr 15, 2009 at 17:36

answered Apr 9, 2009 at 6:09

TStamper

30.4k10 gold badges69 silver badges73 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Chris Brandsma · Accepted Answer · 2009-04-13 23:33:56Z

1

I really don't like option 1 unless you are building a User Control.

I only use the ScriptManager if I'm going to be using the Microsoft AJAX Library on that page. Just putting that there add a lot of extra stuff your page has to download (check it out with Firebug sometime). If you have JavaScript in resource files the ScriptManager can also minify it for you. But that requires recompilation if you JavaScript changes.

I typically use option 3.

answered Apr 13, 2009 at 23:33

Chris Brandsma

11.7k6 gold badges50 silver badges60 bronze badges

Comments

рüффп · Accepted Answer · 2012-04-06 19:38:01Z

1

It depends what you are trying to achieve. The first one adds the script tag to your page during rendering, from the server side. This can be useful for adding dynamically generated JavaScript and things like that.

The second option is only interesting if you're using ASP.NET AJAX for managing your JavaScript, because it registers a whole lot of other JavaScript on the page.

So if you want to keep everything clean and only plan on using jQuery, go with option 3.

edited Apr 6, 2012 at 19:38

рüффп

5,57434 gold badges74 silver badges125 bronze badges

answered Apr 9, 2009 at 6:13

Graffen

2133 silver badges7 bronze badges

Comments

Al W · Accepted Answer · 2009-04-09 06:32:14Z

0

Method #2 works well if I want the js to be included for a certain usercontrol, but not on every page. The scriptmanager also makes sure I don't have duplicate script references. If you want the js included on every page (as jquery will almost always be) then method #3 is cleanest.

answered Apr 9, 2009 at 6:32

Al W

7,7611 gold badge21 silver badges41 bronze badges

Collectives™ on Stack Overflow

Proper way of bringing in jQuery into ASP.NET (or any other external JavaScript)

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related