Thanks, you are right. The runat server attribute meant the server side compiler was trying to deal with the script. So it's fixed now but presents me with a new problem. The reason I put the runat="server" in the script tag is because I am using a MasterPage in my .net web site. A master page is similar to a template where you specify that a new page will include the master page and you have your backgrounds, script tags, banner, nav bar etc included. This is fine until a page in a sub folder uses the master page whereby all links to images, stylesheets etc are broken. That is unless you use the runat="server" attribute which makes the server rsolve the path to the resource for you (URL basing I think it's called)
On Sep 18, 3:05 am, Michael Price <[EMAIL PROTECTED]> wrote: > Jay wrote: > > Having major problems getting anything set up here. > >http://jquery.com/demo/thickbox/ > > > On the above page it says I should download the files mentioned and > > put them in my scripts folder which I did. > > In my page (aspx) I have this > > <script type="text/javascript" src="scripts/jquery-1.2.pack.js" > > runat="server"></script> > > <script type="text/javascript" src="scripts/thickbox.js" > > runat="server"></script> > > I can't claim to be a .NET expert (even though I've been trying to learn > it for three years!) but should those tags have runat="server" in them? > They're meant to be run by the client - this might be your problem. Try > taking the runat attribute out and see if it helps. > > Regards, > Michael Price
