True, but my problem is with a different side of this issue, let me explain a little better:

I have a need to reference an external JS file for my module. The file resides in root/js/Tabs/ folder. To reference that file, I add the following tag < script src="/js/Tabs/tabs2.js" /> the ascx file. It works well for a site with a simple domain name, i.e. http://www.mysite.com/ - as that relative path will translate to http://www.mysite.com/js/Tabs/tabs2.js and correctly point to the file.

HOWEVER! If the site's domain is something like http://www.mysite.com/clientssiteindev, it translates ALSO to http://www.mysite.com/js/Tabs/tabs2.js which is no longer good as http://www.mysite.com/ does not necessarily point to that root directory. The better example is a development scenario in VS 2005 - it creates a path like http://locahost:1651/Website - so http://locahost:1651/js/Tabs/tabs2.js just doesn't exist

I've tried several different techniques to just insert the full path at run time by adding domain name in from of the relative path... to no avail...

Any ideas?

I'd recommend adding the javascript in your modules code-behind via the clientscriptmanager (http://msdn2.microsoft.com/en-us/library/system.web.ui.clientscriptmanager_members.aspx ). As it's server code, you can use the tilde "~" to calculate paths, this will correct build up a path irrespective of whether a site is a parent or a virtual e.g. http://msdn2.microsoft.com/en-us/library/kx145dw2.aspx

@cathal

I agree with you. It just seemed to be such a simple thing to do without getting code involved... :)