ASP.NET Beginner Questions...

[Alex]

Hello everyone,

I'm just beginning to work with ASP.NET and I've run into some issues that I can't seem to solve.

I'm building the master page for a site that can be viewed here: www.cisp.com

The master page has the following javascript includes in the head tag:

    <script type="text/javascript" src="/cisp.net/js/jquery-1.3.2.min.js"></script>
    <script type="text/javascript" src="/cisp.net/js/jquery.accordion-1.2.1.js"></script>
    <script type="text/javascript" src="/cisp.net/js/thickbox-compressed.js"></script>

As you can see, I've had to reference these documents using the "/cisp.net/js/" path in order to get them to properly function across multiple directories.

If I use a path like "~/js/..." or "/js/..." or "js/..." the javascript will either not be pulled into the page at all, or it will only be pulled into root pages and not pages sitting within other directories.

I need to find a way to dynamically hit these from any directory in my website. These files are to be called across all pages of my site, so it would be senseless to not use a master page.

Can anyone lend some assistance?

[unixcommerce]

just switch to PHP .lol

[Alex]

Thank you for that useless post, but you'll need to get with the company I work for to discuss that, I have no play in such a decision.

Issue solved.

[pufa]

/js/jquery-1.3.2.min.js should work if cisp.net is your application root.

[imaginekitty]

/js/jquery-1.3.2.min.js should work if cisp.net is your application root.

That's how I always do it.

[NightStalker-DNS]

One thing to take note of is it depends how ur local environment is set up. /js/jquery doesnt work on my dev site, but it does work on live site. Even tho locally the site folder is the app root.

[Alex]

NightStalker is entirely correct. The issue revolved around how the local web server in Visual Studio was running.

Once I changed the virtual path from "/asp.net" to "/" the application pulled the JavaScript properly. Quite stupid of Visual Studio imho.

Alex

[wwb_99]

Not really--it is all on the developer to get the URLs correctly root relative. See this post for two techniques.

[NightStalker-DNS]

That is true. But in my case I was not using VS server i was also using IIS, but still had the same issue.

[dnectom]

Just set the baseref of the page and then work out where the directory is from based upon this baseref

[phoenixtears]

why dont you use ../ to reach the root director them mention the folder then the file like ../Scripts/Validator.js like that it can work.

[NightStalker-DNS]

why dont you use ../ to reach the root director them mention the folder then the file like ../Scripts/Validator.js like that it can work.

because the same master page would be used for files in the root as well, then that path will be incorrect

[paro]

You could also:

<script type="text/javascript" src="<%= Page.ResolveUrl("~/cisp.net/js/jquery-1.3.2.min.js") %>"></script>

I suppose you could even wrap it in a custom control and have something like this instead:

<ns:ScriptReference Path="~/cisp.net/js/jquery-1.3.2.min.js" />