ASP.NET site, wants to run in subfolder not root!

Matt · 25 Feb 2007 at 15:18

I have some problems... With my ASP.NET 2 site it appears to think the root is up one more level that it really is! This of course means i have a lot of issues with the application working correctly. Does anyone have any ideas on this one? I assume it must be very simple

Thanks

Matt · 25 Feb 2007 at 16:51

Mr^B said:
If you are using Visual Studio's inbuilt web-browser to preview the site, it is normal for you site to appear at root/applicationfolder/ rather than at root/

The solution is here:

http://weblogs.asp.net/scottgu/arch...te-with-the-vs-vwd-2005-local-web-server.aspx

I'm doing that already, it's when i move it to my testing server that i get the problem!

Sorry, i should have mentioned that key bit of information

Matt · 25 Feb 2007 at 18:12

Mr^B said:
Note that this will ONLY work for runat="server" controls.

Yeah i know about that, but i don't want to do that at all. I want to be able to work normally!

I think this must be an IIS issue not a .net one? but i could be wrong

Matt · 25 Feb 2007 at 19:11

It is in the root though... Hence all my confusion!

Matt · 25 Feb 2007 at 19:27

Webserver:
c:\inetpub\wwwroot\Test\Website
http://computer/Test

Dev machine:
c:\projects\Test\Website

On the dev machine all is fine... on the webserver it just won't work

If i change the webserver to:
c:\inetpub\wwwroot\Test
http://computer/Test
It makes no difference at all!

images are in /images.

I can get to them if i do: /Test/images/image.gif
but not: /images/image.gif

Matt · 26 Feb 2007 at 19:09

I should be able to use /images/test.gif, that's how it's always worked in the past, and that's how it is at work! / should take me to the root of the website, not the webserver. It all works fine through VS.net with the built in external tools web server...

Matt · 26 Feb 2007 at 19:59

Mr^B said:
A / reference in a url will ALWAYS go to the root of the webserver (unless you intercept and redirect the request of course).

I have no idea how you managed to achieve this using the built-in web server, all I can think of is that you were using ~/ references instead of /.

Er, aren't relative paths from the website root... This is how it's worked with every site i've ever produced! I'm just confused by what .NET is doing with my site!

Matt · 27 Feb 2007 at 17:57

Ok, clearly my intelligence has been lacking here

You are all correct, i'm am wrong! (again!). I'll look into it again tonight if i can, and should be able to sort it i hope.