There's a mystery I can't understand:

In IIS, there is Default Web Site.
Microsoft expects (in InterDev and VS.NET) that any application I create
will reside under the Default Web Site, that is: http://localhost/something,
and doesn't let me create a different ROOT web site (which will be assigned
a different port and will be at the same level as Default Web Site).

The effect is that all across my application (web site) I won't be able to
refer to the root of the site by just slash - "/". I must refer to something
like "/something/default.aspx".

On the other hand, when my site will be depolyed on a live server, it will
be (I believe it should...) a root web site and not a subfolder that is
simply conifgured as an application, so all my references to
"/something/default.aspx" will be wrong - because in the server, the
reference should be only "/default.aspx".

Another view of the same problem: In classic ASP, I have an Includes folder
in which I have a file called Template.asp which holds (how surprising) the
top and down template and is referenced by all other ASPs in <!--
Include --> directive. I also have an Images folder which holds all the
images.
The problem is that this template is included by many ASPs - some of them
are in the root folder, some of them are in subfolders. So when I want to
refer to some image, if I'll type "images/ball.gif" it will work only in
ASPs which reside in the root folder - if they reside under a subfolder, the
reference will be wrong. The ideal is to type "/images/ball.gif" - but a-ha!
If I have to follow Microsoft's rules, this would be wrong, because the root
according to Microsoft (Interdev/VS.NET) should be "http://something/"...

What's the best to do? How can I overcome this conflict?

Thanks

"Ofer" <ofer> wrote in message
news:1184
> There's a mystery I can't understand:

Responded to in an earlier thread ...