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: [url down],
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

you need to format your hard disk then install Linux or throw your computer for charity ...

"Ofer" <ofer> wrote in message
news:1760
> 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:
[url down],
> 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).
Hi Ofer,

True that VS.NET assumes virtual directories.

True as well that IF you develop on Windows 2000 server or better, you CAN
use virtual webservers by using host-headers.

Third true is, that you can COPY-PASTE deploy your scripts and binaries to a
production website without using VS.NET or something.

Much success

"R.K" <anonymous> wrote in message
news:65fc
> you need to format your hard disk then install Linux or throw your
computer for charity ...

I understand that you have problems with the superiority of IIS 6 above
Linux&apache.

Egbert , You didn't answer the question!

"Egbert Nierop (MVP for IIS)" <egbert_nierop> wrote in message
news:2412
[..]

"Ofer" <ofer> wrote in message
news:1760
> 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:
[url down],
> 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).

That's not true at all. You have to first configure the new site (virtual
server) using the IIS MMC - it can't be done from Visual Studio.

> 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?

I'm not following your problem here. If you use a path without the initial
"/", then you're referring to a resource within the current directory.