Hello,
Could anybody explain what's a difference between a virtual directory and an
application root under IIS? I'm a little bit confused.
This is mu problem:
Let's assume the following directory structure:
FileManager (application name a.k.a. virtual directory?)
Images
header.gif
Styles
styles.css
Scripts
start.aspx
The start.aspx script utilizes the images and styles in the following way:
<link rel="stylesheet" href="/FileManager/Styles/styles.css"
type="text/css">
<img src="/FileManager/Images/header.gif">
That's fine when the name of the virtual directory is "FileManager", but it
might be different. I do not know the name when I design start.aspx. I would
prefer to use something like this:
<link rel="stylesheet" href="/Styles/styles.css" type="text/css">
<img src="/Images/header.gif">
I can use this syntax on Unix (/ means "start from the root directory" - I
do not need to provide the directory name), but it seems IIS requires the
application name.
Am I doing something wrong? Is there any solution for this issue?
Thanks,
Leszek Taratuta 5 3653
Hello Lszek,
A virtual directory is a "pointer" to a physical directory. Example, files
on www.MySite.com are not actually stored there, more likely, they are
stored in c:\inetpub\wwwroot\mysitecom\ . The rootlevel wil allways be a
virtual directory (MySite.com/). You can add other virtual roots, example,
"MySite.com/Images" could point to "c:\documents\alex\pictures\". These VDs
are set up in IIS.
An application root is a type of virtual directory that isolates the
Sessions and Configuration for everything in the folder it's in. By
default, the RootLevel (Mysite.com/) will be an application root. You can,
however, define other applications. For example, if you had the application
MySite/Application1, and also had MySite/Application2, users logged into the
former would not be logged into the latter. they aplications are isolated
from eachother.
I hope this clears things up. Just reply if you have more questions.
Alex Papadimoulis
"Leszek" <ta******@5thbusiness.com> wrote in message
news:#j**************@tk2msftngp13.phx.gbl... Hello,
Could anybody explain what's a difference between a virtual directory and
an application root under IIS? I'm a little bit confused.
This is mu problem:
Let's assume the following directory structure:
FileManager (application name a.k.a. virtual directory?) Images header.gif Styles styles.css Scripts start.aspx
The start.aspx script utilizes the images and styles in the following way: <link rel="stylesheet" href="/FileManager/Styles/styles.css" type="text/css"> <img src="/FileManager/Images/header.gif">
That's fine when the name of the virtual directory is "FileManager", but
it might be different. I do not know the name when I design start.aspx. I
would prefer to use something like this: <link rel="stylesheet" href="/Styles/styles.css" type="text/css"> <img src="/Images/header.gif">
I can use this syntax on Unix (/ means "start from the root directory" - I do not need to provide the directory name), but it seems IIS requires the application name. Am I doing something wrong? Is there any solution for this issue?
Thanks, Leszek Taratuta
Thanks a lot. Now I understand the difference between a virtual directory
and an application root.
Although I still do not know how to be independent from the application
name. I would like to use URLs like this:
/images/myimage.gif
instead of
/myapp/images/myimage.gif
("myapp" is the application root)
Should I define another virtual directory on the images folder? What about
other folders I would like to treat the same way?
Let's say I have the following folders:
c:\inetpub\wwwroot\myapp\images
c:\inetpub\wwwroot\myapp\catalogimages
c:\inetpub\wwwroot\myapp\styles
c:\inetpub\wwwroot\myapp\controls
c:\inetpub\wwwroot\myapp\examples
etc.
My application root is defined on c:\inetpub\wwwroot\myapp.
I would like to use "\images", "\catalogimages", "\styles", etc instead of
"\myapp\images", "\myapp\catalogimages", "\myapp\styles" with as little
hassle as possible?
Thanks for any advice,
Leszek Taratuta
"Alex Papadimoulis" <alexp-at-halogenstudios.com> wrote in message
news:#8**************@TK2MSFTNGP09.phx.gbl... Hello Lszek,
A virtual directory is a "pointer" to a physical directory. Example, files on www.MySite.com are not actually stored there, more likely, they are stored in c:\inetpub\wwwroot\mysitecom\ . The rootlevel wil allways be a virtual directory (MySite.com/). You can add other virtual roots,
example, "MySite.com/Images" could point to "c:\documents\alex\pictures\". These
VDs are set up in IIS.
An application root is a type of virtual directory that isolates the Sessions and Configuration for everything in the folder it's in. By default, the RootLevel (Mysite.com/) will be an application root. You
can, however, define other applications. For example, if you had the
application MySite/Application1, and also had MySite/Application2, users logged into
the former would not be logged into the latter. they aplications are isolated from eachother.
I hope this clears things up. Just reply if you have more questions.
Alex Papadimoulis
"Leszek" <ta******@5thbusiness.com> wrote in message news:#j**************@tk2msftngp13.phx.gbl... Hello,
Could anybody explain what's a difference between a virtual directory
and an application root under IIS? I'm a little bit confused.
This is mu problem:
Let's assume the following directory structure:
FileManager (application name a.k.a. virtual directory?) Images header.gif Styles styles.css Scripts start.aspx
The start.aspx script utilizes the images and styles in the following
way: <link rel="stylesheet" href="/FileManager/Styles/styles.css" type="text/css"> <img src="/FileManager/Images/header.gif">
That's fine when the name of the virtual directory is "FileManager", but it might be different. I do not know the name when I design start.aspx. I would prefer to use something like this: <link rel="stylesheet" href="/Styles/styles.css" type="text/css"> <img src="/Images/header.gif">
I can use this syntax on Unix (/ means "start from the root directory" -
I do not need to provide the directory name), but it seems IIS requires
the application name. Am I doing something wrong? Is there any solution for this issue?
Thanks, Leszek Taratuta
Hi Leszek,
It is certainly possible, but it depends on your development enviornment.
If you develop on a 2000/XP Pro box, then you are allowed only one "site"
(i.e., root level), which is why you have to use a subdirectory
(localhost/myapp). This leaves you with a few options:
1. Develop on your machine using all relative URLs (instead of
"/myapp/images/image.gif", use "../images/image.gif", or whatever), and
deploy the application to the server's root URL
2. Get a development server, and develop directly on the server, instead of
the local machine.
3. Change your OS to a server OS, so you can be allowed different sites
If you go with #2 or #3, you'll want to set up different sites in IIS.
I use #2, and have a whole subnet dedicated to development sites (i.e.,
192.168.100.xxx are development sites). One issue you'll probably run into
if you go with #2 is debugging on the server. I was never able to get it to
work, so I dont even bother, but then again, I found using VS.net to develop
websites just too much of a PITA.
Codebehind, horrible HTML handling, bad code generation, oooh I could go
on --- Whidbey's looking promising, but for now, it's Dreamweaver for me.
(Dont get me wrong tho, VS.net is essneital to create middle tier, it just
rellly fails on the web site).
Alex Papadimoulis
"Leszek" <ta******@5thbusiness.com> wrote in message
news:##**************@TK2MSFTNGP12.phx.gbl... Thanks a lot. Now I understand the difference between a virtual directory and an application root. Although I still do not know how to be independent from the application name. I would like to use URLs like this: /images/myimage.gif instead of /myapp/images/myimage.gif ("myapp" is the application root)
Should I define another virtual directory on the images folder? What about other folders I would like to treat the same way? Let's say I have the following folders: c:\inetpub\wwwroot\myapp\images c:\inetpub\wwwroot\myapp\catalogimages c:\inetpub\wwwroot\myapp\styles c:\inetpub\wwwroot\myapp\controls c:\inetpub\wwwroot\myapp\examples etc.
My application root is defined on c:\inetpub\wwwroot\myapp. I would like to use "\images", "\catalogimages", "\styles", etc instead of "\myapp\images", "\myapp\catalogimages", "\myapp\styles" with as little hassle as possible?
Thanks for any advice, Leszek Taratuta
"Alex Papadimoulis" <alexp-at-halogenstudios.com> wrote in message news:#8**************@TK2MSFTNGP09.phx.gbl... Hello Lszek,
A virtual directory is a "pointer" to a physical directory. Example,
files on www.MySite.com are not actually stored there, more likely, they are stored in c:\inetpub\wwwroot\mysitecom\ . The rootlevel wil allways be
a virtual directory (MySite.com/). You can add other virtual roots, example, "MySite.com/Images" could point to "c:\documents\alex\pictures\". These VDs are set up in IIS.
An application root is a type of virtual directory that isolates the Sessions and Configuration for everything in the folder it's in. By default, the RootLevel (Mysite.com/) will be an application root. You can, however, define other applications. For example, if you had the application MySite/Application1, and also had MySite/Application2, users logged into the former would not be logged into the latter. they aplications are
isolated from eachother.
I hope this clears things up. Just reply if you have more questions.
Alex Papadimoulis
"Leszek" <ta******@5thbusiness.com> wrote in message news:#j**************@tk2msftngp13.phx.gbl... Hello,
Could anybody explain what's a difference between a virtual directory and an application root under IIS? I'm a little bit confused.
This is mu problem:
Let's assume the following directory structure:
FileManager (application name a.k.a. virtual directory?) Images header.gif Styles styles.css Scripts start.aspx
The start.aspx script utilizes the images and styles in the following way: <link rel="stylesheet" href="/FileManager/Styles/styles.css" type="text/css"> <img src="/FileManager/Images/header.gif">
That's fine when the name of the virtual directory is "FileManager",
but it might be different. I do not know the name when I design start.aspx. I would prefer to use something like this: <link rel="stylesheet" href="/Styles/styles.css" type="text/css"> <img src="/Images/header.gif">
I can use this syntax on Unix (/ means "start from the root
directory" - I do not need to provide the directory name), but it seems IIS requires the application name. Am I doing something wrong? Is there any solution for this issue?
Thanks, Leszek Taratuta
Thanks a lot.
For now I will stick to the first option (relative URLs).
I am also going to try developing directly on the server instead of my local
machine. You are right there are some debugging issues, but I hope I will
resolve them.
In the future it is a good idea to have a server locally.
IMHO
VS.NET is not bad. I'm using Dreamweaver just for visual desing. For
coding - VS.NET.
Thanks again for your help,
Leszek Taratuta
"Alex Papadimoulis" <alexp-at-halogenstudios.com> wrote in message
news:eF*************@TK2MSFTNGP09.phx.gbl... Hi Leszek,
It is certainly possible, but it depends on your development enviornment. If you develop on a 2000/XP Pro box, then you are allowed only one "site" (i.e., root level), which is why you have to use a subdirectory (localhost/myapp). This leaves you with a few options: 1. Develop on your machine using all relative URLs (instead of "/myapp/images/image.gif", use "../images/image.gif", or whatever), and deploy the application to the server's root URL 2. Get a development server, and develop directly on the server, instead
of the local machine. 3. Change your OS to a server OS, so you can be allowed different sites
If you go with #2 or #3, you'll want to set up different sites in IIS.
I use #2, and have a whole subnet dedicated to development sites (i.e., 192.168.100.xxx are development sites). One issue you'll probably run
into if you go with #2 is debugging on the server. I was never able to get it
to work, so I dont even bother, but then again, I found using VS.net to
develop websites just too much of a PITA. Codebehind, horrible HTML handling, bad code generation, oooh I could go on --- Whidbey's looking promising, but for now, it's Dreamweaver for me. (Dont get me wrong tho, VS.net is essneital to create middle tier, it just rellly fails on the web site).
Alex Papadimoulis
"Leszek" <ta******@5thbusiness.com> wrote in message news:##**************@TK2MSFTNGP12.phx.gbl... Thanks a lot. Now I understand the difference between a virtual
directory and an application root. Although I still do not know how to be independent from the application name. I would like to use URLs like this: /images/myimage.gif instead of /myapp/images/myimage.gif ("myapp" is the application root)
Should I define another virtual directory on the images folder? What
about other folders I would like to treat the same way? Let's say I have the following folders: c:\inetpub\wwwroot\myapp\images c:\inetpub\wwwroot\myapp\catalogimages c:\inetpub\wwwroot\myapp\styles c:\inetpub\wwwroot\myapp\controls c:\inetpub\wwwroot\myapp\examples etc.
My application root is defined on c:\inetpub\wwwroot\myapp. I would like to use "\images", "\catalogimages", "\styles", etc instead
of "\myapp\images", "\myapp\catalogimages", "\myapp\styles" with as little hassle as possible?
Thanks for any advice, Leszek Taratuta
"Alex Papadimoulis" <alexp-at-halogenstudios.com> wrote in message news:#8**************@TK2MSFTNGP09.phx.gbl... Hello Lszek,
A virtual directory is a "pointer" to a physical directory. Example, files on www.MySite.com are not actually stored there, more likely, they are stored in c:\inetpub\wwwroot\mysitecom\ . The rootlevel wil allways
be a virtual directory (MySite.com/). You can add other virtual roots, example, "MySite.com/Images" could point to "c:\documents\alex\pictures\".
These VDs are set up in IIS.
An application root is a type of virtual directory that isolates the Sessions and Configuration for everything in the folder it's in. By default, the RootLevel (Mysite.com/) will be an application root. You can, however, define other applications. For example, if you had the application MySite/Application1, and also had MySite/Application2, users logged
into the former would not be logged into the latter. they aplications are isolated from eachother.
I hope this clears things up. Just reply if you have more questions.
Alex Papadimoulis
"Leszek" <ta******@5thbusiness.com> wrote in message news:#j**************@tk2msftngp13.phx.gbl... > Hello, > > Could anybody explain what's a difference between a virtual
directory and an > application root under IIS? I'm a little bit confused. > > This is mu problem: > > Let's assume the following directory structure: > > FileManager (application name a.k.a. virtual directory?) > Images > header.gif > Styles > styles.css > Scripts > start.aspx > > The start.aspx script utilizes the images and styles in the
following way: > <link rel="stylesheet" href="/FileManager/Styles/styles.css" > type="text/css"> > <img src="/FileManager/Images/header.gif"> > > That's fine when the name of the virtual directory is "FileManager", but it > might be different. I do not know the name when I design start.aspx.
I would > prefer to use something like this: > <link rel="stylesheet" href="/Styles/styles.css" type="text/css"> > <img src="/Images/header.gif"> > > I can use this syntax on Unix (/ means "start from the root directory" - I > do not need to provide the directory name), but it seems IIS
requires the > application name. > Am I doing something wrong? Is there any solution for this issue? > > Thanks, > Leszek Taratuta > >
"Leszek" wrote: Thanks a lot. Now I understand the difference between a virtual directory and an application root. Although I still do not know how to be independent from the application name. I would like to use URLs like this: /images/myimage.gif instead of /myapp/images/myimage.gif ("myapp" is the application root)
You can use ~/images/myimage.gif
"~" references the web app's root directory.
Cheers,
--
Joerg Jooss jo*********@gmx.net This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Jeffry van de Vuurst |
last post by:
Hi,
(sorry for the crosspost, I wasn't sure which was the best place to
put this).
I was just thinking about something and wondered if any of you has
some ideas about this.
I'm using the...
|
by: Michelle |
last post by:
I have a website with 6 virtual directories under it who dont "see" the bin/
directory in the root.
If I create a /bin directory in each virtual directory and then copy my
dll's in there, it...
|
by: Sheila Jones |
last post by:
Hello,
Could somebody explain (or point me to a website that does) the difference
between a 'virtual directory' and an 'application root'? I don't really get
it at the moment. Thanks.
|
by: nick |
last post by:
I have a problem and I've been using a cheezy work around and was
wondering if anyone else out there has a better solution.
The problem:
Let's say I have a web application appA. Locally, I set...
|
by: Lasse Nilsson |
last post by:
Hi all,
I've got a deployment issue I hope is solvable at all, and appreciate all
help anyone can give me.
We've got an ASP.NET-application (a sort of function library shared by our
customers,...
| |
by: Manso |
last post by:
Hi,
We have an application that is installed in default web site (root web
site). The same application will be installed as virtual directories under
the root site e.g. <default web site>/app1...
|
by: Chuck P |
last post by:
Using vs05 and making an asp.net 2.0 website.
We use VSS and have everything organized like this
SolutionName
Documents
Code
WebProjectName1
WebServiceProjectName1
|
by: djmc |
last post by:
Hi,
I am having problems with virtual directories and web.config inheritance. I
have read the section titled "Conflicts between settings on virtual and
physical directories" at...
|
by: Paul F |
last post by:
Im confused about the difference(s) between virtual directories and
physical
directories in IIS.
Any ideas?
*** Sent via Developersdex http://www.developersdex.com ***
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
| |
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated ...
| |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence...
| |