Website Design Question

Factual Questions
1

I’m working on a web site called “foo” locally: http://localhost/foo/.

%foo% is a virtual directory in IIS:

Default Web Site
foo

(There are other virtual directories (web sites) under Default Web Site)

Now, when I deploy to a host, foo is going to be the domain name (www.foo.com). What is my directory structure going to look like when I deploy to a host? - http://www.foo.com/foo/? Obviously, I don’t want this. I just want http://www.foo.com/.

Does this make sense? The virtual directories in IIS are confusing me. Do I need to work within the root of ‘Default Web Site’ to keep the proper directory structure when I deploy to a host? If so, that seems to defeat the purpose of virtual directories.

And what about my relative URI’s?

Thanks

2

If you have relative URLs then the entire directory structure will always work assuming you keep the heirarchy the same, even if you move it up or down a level.

i don’t know how IIS works, though.

3

Generally speaking (this is not IIS-specific, just the way such things generally work in my experience) your localhost directory would be the equivalent of the root of your remote host structure.

So, if you have a local structure like so:

http://localhost/foo/
http://localhost/foo/images/

Once deployed, your remote directory structure would be, respectively, like so:

http://www.foo.com/
http://www.foo.com/images/

This assumes you are using relative addressing, of course, which I’m pretty sure is default in most cases.