ansaurus

Question

ASP.Net Master Page and File path issues

Answer 1

A:

<script type="text/javascript" src="/full/path/to/jquery.js"></script>

karim79 2009-03-30 15:21:37

Answer 2

+10 A:

Try:

<asp:ScriptManager ID="ScriptManager1" runat="server">
    <Scripts>
        <asp:ScriptReference Path="~/jquery.js" />
    </Scripts>
</asp:ScriptManager>

EDIT:

If you REALLY need this in your <head> section, you could do something like:

<script type="text/javascript" src="<%= Page.ResolveClientUrl("~/jquery.js") %>"></script>

Cory Larson 2009-03-30 15:22:49

Aye, this is a highly recommended method in a lot of ASP.NET books I've written when dealing with paths in masterpages.

Kezzer 2009-03-30 15:57:32

Check "Edit 2" of my original post. Thanks for your help BTW

TheDude 2009-03-30 17:40:12

FYI, my co-worker and I just tried this out. This doesn't seem to work in a nested master page scenario *in the parent master page*. Moving it to the child master page, however, did the trick.

technomalogical 2009-08-11 20:13:00

Answer 3

A:

If this script tag goes directly to the browser, then you unlikely can substitute your site's root there. At least not on the server. So you can:

Deploy site to the root of domain name and use absolute paths (simplest solution).
Insert this link with server control.
Preprocess resulting HTML before sending it to the client (with HttpResponse.Filter).

XOR 2009-03-30 15:24:20

Answer 4

+2 A:

If you're not going to us asp:ScriptManager or absolute paths then you can do it like this:

<script runat="server" type="text/javascript" 
  src='<%= Page.ResolveUrl("~/jquery.js") %>'></script>

Keltex 2009-03-30 15:26:42

Answer 5

A:

You can also use <base> HTML tag:

<base href="http://www.domain.com"&gt;&lt;/base&gt;

and then all the links in header section are relative to base address:

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

It's often useful when you have multiple publishing destinations, like local dev web server, demo server, etc. You just replace that base URL.

Hrvoje 2009-03-30 15:40:06

Answer 6

+2 A:

I do not know whether you guys found the solution to your problem or not. I was facing the same problem and going nuts to figure out why do I get "jQuery is undefined" error on the plugins i use. I tried all the solutions i get from the internet but no luck at all.

But, suddenly something splash on my mind that may be the script files should be in order. So, I moved the jquery referece to first position and everything start working like charm.

Remember guys, if you're using any plugins with jquery, make sure you use the folloing order of setting reference to those fiels.

reference to the jquery library
reference to the other subsequent plug-in libraries and so on...

e.g.:

"script src="js/jquery-1.3.2.min.js" type="text/javascript"...
"script src="js/jqDnR.min.js" type="text/javascript"...
"script src="js/jquery.jqpopup.min.js" type="text/javascript"...
"script src="js/jquery.bgiframe.min.js" type="text/javascript"...

Always make sure you must put the jquery reference to first and then the subsequent libraries.

Hope, this solves your problem especially when you use with MasterPages. Its very strange that it works no matter what order you use when you don't use MasterPages but when you do, then it somehow requres the proper order.

Good luck and happy coding,

Vincent D'Souza

2009-08-31 12:58:31

Thanks for this tip!

tbone 2010-02-26 18:21:56

Answer 7

A:

You can also make the head tag runat="server" and then use the ~ directive in your script includes. You don't want to make your script blocks runat="server" unless they are meant to be server-side code.

<head runat="server">
  <script src="~/jquery.js" ></script>
</head>

KOTJMF 2009-08-31 13:04:56

ansaurus

tags:

views:

answers:

ASP.Net Master Page and File path issues

related questions