Jay ha scritto:
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)
Don't know .NET, but if I understand the problem this tag can be useful:
http://www.w3schools.com/tags/tag_base.asp bye
