This is a basic question but I can't find any literature on it:

When I use the browser to run somepage.aspx , localhost refers to the IIS (I think).
Do I have to put the file in inetpub/wwwroot folder for it be accessed as localhost?

Can I put the file on the C: drive then make the folder containing the somepage.aspx a virtual folder but still call the localhost?

The confusion is: When I make the folder into a virtual folder in the IIS I get that global icon. Does this make it reside in the localhost?

Do I have this all wrong?

What does localhost truely mean?

Thank you so much.

When you use the browser to run somepage.aspx , localhost refers to the default directory which is mapped in your harddisk as localhost.

Do I have to put the file in inetpub/wwwroot folder for it be accessed as localhost?

** This is default, but you can modify this.

Can I put the file on the C: drive then make the folder containing
the somepage.aspx a virtual folder but still call the localhost?

** You can create folder at some other location and call it as localhost/your folder (For this you need to map virtually).

Check the following article :

http://www.developer.com/net/asp/art...0917_1588231_2

hope this helps...




Om Prakash

localhost is a TCP/IP alias name for your local PC. It maps to IP address 127.0.0.1.

The book makes the assumption that you want to run the web site on your own computer.

IIS has it's own directory structure that's visible from the web. The "virtual root" directory is the one that is accessed from the web as http://localhost/.
This does not refer to your root folder on drive C. Instead, IIS lets you specify the actual directory on your hard disk that will map to the virtual root.

By default, c:\inetpub\wwwroot will be the directory on your hard disk that maps to http://localhost/.

ThePhile is not set up to run from the virtual root directory. Instead, they want you to set up another virtual directory named "ThePhile" or "ThePhileVB" that will map to the appropriate directory on your hard disk.

This book isn't a good "first book" to study on ASP.NET. There are a lot of assumptions made along the way. You might want to pick up an intro book on ASP.NET before you try to tackle this one.

Eric