Comments on: Path resolution in ASP.NET http://quickduck.com/blog/2010/01/14/path-resolution-in-asp-net/ Straight from the mind of geniuseseses.... Fri, 06 Aug 2010 07:40:27 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: Nelson http://quickduck.com/blog/2010/01/14/path-resolution-in-asp-net/comment-page-1/#comment-11977 Nelson Fri, 07 May 2010 20:05:07 +0000 http://quickduck.com/blog/?p=249#comment-11977 Actually, using master pages won't resolve it, because the path is still relative to the derived pages. If you have derived pages in several subfolders it's nearly impossible to get it working. With runat=server, I think I have had ASP.NET throw a parsing error, probably because it doesn't know what to do with the actual JavaScript/CSS/whatever content. I may be wrong, though... Actually, using master pages won’t resolve it, because the path is still relative to the derived pages. If you have derived pages in several subfolders it’s nearly impossible to get it working. With runat=server, I think I have had ASP.NET throw a parsing error, probably because it doesn’t know what to do with the actual JavaScript/CSS/whatever content. I may be wrong, though…

]]> By: Drew http://quickduck.com/blog/2010/01/14/path-resolution-in-asp-net/comment-page-1/#comment-11943 Drew Sun, 24 Jan 2010 03:57:23 +0000 http://quickduck.com/blog/?p=249#comment-11943 Ah yes I follow now. If your head tag is set to "runat=server" you can you the "~" key to resolve the path from the application root as well. Or using master pages could eliminate the need for it as well. Ah yes I follow now. If your head tag is set to “runat=server” you can you the “~” key to resolve the path from the application root as well. Or using master pages could eliminate the need for it as well.

]]> By: Gerrod http://quickduck.com/blog/2010/01/14/path-resolution-in-asp-net/comment-page-1/#comment-11930 Gerrod Fri, 15 Jan 2010 08:59:46 +0000 http://quickduck.com/blog/?p=249#comment-11930 Hey Drew - using "scripts/jquery" would only work if the file that is loading the script is in the root of the website. If your page was "mywebsite/accounts/default.aspx" it would look for a "scripts" folder under the "accounts" folder. And yes, you're absolutely right about serving jquery from Microsoft or Google, but this can be applied for any resource - your own javascript files or images, for example... Hey Drew – using “scripts/jquery” would only work if the file that is loading the script is in the root of the website. If your page was “mywebsite/accounts/default.aspx” it would look for a “scripts” folder under the “accounts” folder.

And yes, you’re absolutely right about serving jquery from Microsoft or Google, but this can be applied for any resource – your own javascript files or images, for example…

]]> By: Drew http://quickduck.com/blog/2010/01/14/path-resolution-in-asp-net/comment-page-1/#comment-11929 Drew Thu, 14 Jan 2010 22:05:46 +0000 http://quickduck.com/blog/?p=249#comment-11929 Or you could always serve jquery from google or microsoft's CDN. Or you could always serve jquery from google or microsoft’s CDN.

]]> By: Drew http://quickduck.com/blog/2010/01/14/path-resolution-in-asp-net/comment-page-1/#comment-11928 Drew Thu, 14 Jan 2010 21:53:47 +0000 http://quickduck.com/blog/?p=249#comment-11928 The url would work in both production and development if you changed the href to "Scripts/jquery.js" as well. The url would work in both production and development if you changed the href to “Scripts/jquery.js” as well.

]]>